public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jakub Jelen <jjelen@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/libmodsecurity] rawhide: Verify source signatures with openpgpverify
Date: Sat, 21 Nov 2026 14:25:13 GMT	[thread overview]
Message-ID: <179527111358.1.18151029063142091906.rpms-libmodsecurity-bada0f8783f3@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/libmodsecurity
            Branch : rawhide
            Commit : bada0f8783f3a507b399aeff1b19dc4e6691a624
            Author : Jakub Jelen <jjelen@redhat.com>
            Date   : 2026-11-03T09:46:33+01:00
            Stats  : +2/-2 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/libmodsecurity/c/bada0f8783f3a507b399aeff1b19dc4e6691a624?branch=rawhide

            Log:
            Verify source signatures with openpgpverify

Replace the GnuPG-based %gpgverify with %openpgpverify, which uses
Sequoia sqv and takes the same options, as part of the Fedora 45 Change
https://fedoraproject.org/wiki/Changes/Sequoia_openpgpverify

Assisted-by: Claude Opus 5.5

---
diff --git a/libmodsecurity.spec b/libmodsecurity.spec
index 3be96ea..6ea8d9c 100644
--- a/libmodsecurity.spec
+++ b/libmodsecurity.spec
@@ -16,7 +16,7 @@ BuildRequires: flex
 BuildRequires: gcc-c++
 BuildRequires: git-core
 # for gpg verification
-BuildRequires: gnupg2
+BuildRequires: openpgpverify
 BuildRequires: make
 BuildRequires: pkgconfig(libcurl)
 %if 0%{?fedora} || 0%{?rhel} >= 9
@@ -62,7 +62,7 @@ applications that use %{name}.
 
 
 %prep
-%{gpgverify} --keyring='%{SOURCE2}' --signature='%{SOURCE1}' --data='%{SOURCE0}'
+%{openpgpverify} --keyring='%{SOURCE2}' --signature='%{SOURCE1}' --data='%{SOURCE0}'
 %autosetup -n modsecurity-v%{version} -S git
 
 

                 reply	other threads:[~2026-11-21 14:25 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=179527111358.1.18151029063142091906.rpms-libmodsecurity-bada0f8783f3@fedoraproject.org \
    --to=jjelen@redhat.com \
    --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