public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/lcmaps] epel10.2: Update lcmaps.spec
Date: Tue, 28 Jul 2026 15:20:52 GMT	[thread overview]
Message-ID: <178525205225.1.13686299452451303334.rpms-lcmaps-e6a62e147245@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/lcmaps
            Branch : epel10.2
            Commit : e6a62e1472454452bf209650e29e0c058f4fe0fe
            Author : Mischa Sallé <msalle@nikhef.nl>
            Date   : 2019-02-04T16:27:39+00:00
            Stats  : +8/-7 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/lcmaps/c/e6a62e1472454452bf209650e29e0c058f4fe0fe?branch=epel10.2

            Log:
            Update lcmaps.spec

- Update globus dependencies
- Remove obsolete comments
- Replace lcmaps-interface with lcmaps-devel in descriptions

---
diff --git a/lcmaps.spec b/lcmaps.spec
index 65c765f..6bb9afc 100644
--- a/lcmaps.spec
+++ b/lcmaps.spec
@@ -18,17 +18,16 @@
 Summary: Grid (X.509) and VOMS credentials to local account mapping service
 Name: lcmaps
 Version: 1.6.5
-Release: 10%{?dist}
+Release: 11%{?dist}
 License: ASL 2.0
 URL: http://wiki.nikhef.nl/grid/LCMAPS
 Source0: http://software.nikhef.nl/security/lcmaps/lcmaps-%{version}.tar.gz
-# BuildRoot is still required for EPEL5
-BuildRequires:  gcc
-BuildRequires: globus-core
+BuildRequires: gcc
 BuildRequires: globus-common-devel
 BuildRequires: globus-gssapi-gsi-devel
 BuildRequires: globus-gss-assist-devel
 BuildRequires: globus-gsi-credential-devel
+BuildRequires: globus-gsi-proxy-core-devel
 BuildRequires: voms-devel
 BuildRequires: flex, bison
 
@@ -88,7 +87,7 @@ account based on the site local policy.
 It is a highly configurable pluggable interface, and many plugins are
 available to tailor almost every need. Since this is middleware, it
 does not interact with the user directly; to use it in a program please
-see the lcmaps-interface package.
+see the lcmaps-devel package.
 
 This package contains the files necessary to compile and link
 against the LCMAPS library.
@@ -133,7 +132,7 @@ account based on the site local policy.
 It is a highly configurable pluggable interface, and many plugins are
 available to tailor almost every need. Since this is middleware, it
 does not interact with the user directly; to use it in a program please
-see the lcmaps-interface package.
+see the lcmaps-devel package.
 
 This package contains the development libraries to build
 without the GSI protocol.
@@ -190,7 +189,6 @@ mkdir -p ${RPM_BUILD_ROOT}%{_libdir}/lcmaps
 # clean up installed files
 rm -rf ${RPM_BUILD_ROOT}%{_docdir}
 
-# Retain the clean section for EPEL5
 %ldconfig_scriptlets
 
 %ldconfig_scriptlets without-gsi
@@ -290,6 +288,9 @@ rm -rf ${RPM_BUILD_ROOT}%{_docdir}
 
 
 %changelog
+* Mon Feb  4 2019 Mischa Sallé <msalle@nikhef.nl> 1.6.5-11
+- Update globus dependencies
+
 * Fri Feb 01 2019 Fedora Release Engineering <releng@fedoraproject.org> - 1.6.5-10
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
 

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-28 15:20  [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-07-28 15:20 [rpms/lcmaps] epel10.2: Update lcmaps.spec 

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=178525205225.1.13686299452451303334.rpms-lcmaps-e6a62e147245@fedoraproject.org \
    --to=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