public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Dennis van Dok <dennisvd@nikhef.nl>
To: git-commits@fedoraproject.org
Subject: [rpms/lcmaps] epel10.2: Patch the example DB file so it doesn't contain an architecture-specific path. Fixes bug #1034019.
Date: Tue, 28 Jul 2026 15:20:41 GMT	[thread overview]
Message-ID: <178525204161.1.14971537659709591523.rpms-lcmaps-27abe636bf80@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/lcmaps
Branch : epel10.2
Commit : 27abe636bf80ef56e498ecb39b7256833dc59f49
Author : Dennis van Dok <dennisvd@nikhef.nl>
Date   : 2013-11-25T12:22:30+01:00
Stats  : +9/-1 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/lcmaps/c/27abe636bf80ef56e498ecb39b7256833dc59f49?branch=epel10.2

Log:
Patch the example DB file so it doesn't contain an architecture-specific path. Fixes bug #1034019.

---
diff --git a/lcmaps.spec b/lcmaps.spec
index 9976dac..d7df7b2 100644
--- a/lcmaps.spec
+++ b/lcmaps.spec
@@ -18,11 +18,14 @@
 Summary: Grid (X.509) and VOMS credentials to local account mapping service
 Name: lcmaps
 Version: 1.6.1
-Release: 6%{?dist}
+Release: 7%{?dist}
 License: ASL 2.0
 Group: System Environment/Libraries
 URL: http://wiki.nikhef.nl/grid/LCMAPS
 Source0: http://software.nikhef.nl/security/lcmaps/lcmaps-%{version}.tar.gz
+# Remove the architecture specific element from the example db file
+# https://bugzilla.nikhef.nl/show_bug.cgi?id=18
+Patch0: lcmaps-1.6.1-dbfile-path.patch
 # BuildRoot is still required for EPEL5
 BuildRoot: %(mktemp -ud %{_tmppath}/%{name}-%{version}-%{release}-XXXXXX)
 BuildRequires: globus-core
@@ -146,6 +149,7 @@ without the GSI protocol.
 
 %prep
 %setup -q
+%patch0 -p1
 
 %build
 
@@ -301,6 +305,10 @@ rm -rf $RPM_BUILD_ROOT
 
 
 %changelog
+* Mon Nov 25 2013 Dennis van Dok <dennisvd@nikhef.nl> 1.6.1-7
+- Patch the example DB file so it doesn't contain an
+  architecture-specific path. Fixes bug #1034019.
+
 * Tue Nov 12 2013 Dennis van Dok <dennisvd@nikhef.nl> 1.6.1-6
 - Make requirements arch-specific for devel package
 

                 reply	other threads:[~2026-07-28 15:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178525204161.1.14971537659709591523.rpms-lcmaps-27abe636bf80@fedoraproject.org \
    --to=dennisvd@nikhef.nl \
    --cc=git-commits@fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox