public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Colin Walters <walters@verbum.org>
To: git-commits@fedoraproject.org
Subject: [rpms/fedora-repos] f45: Remove spurious space ` ` in RPM-GPG-KEY-fedora-37-primary
Date: Mon, 10 Aug 2026 09:41:16 GMT	[thread overview]
Message-ID: <178635487666.1.8746471665101878948.rpms-fedora-repos-d501e7f0a46d@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/fedora-repos
            Branch : f45
            Commit : d501e7f0a46db16be88a46d0bba981d7f4684c09
            Author : Colin Walters <walters@verbum.org>
            Date   : 2021-08-16T16:58:41-04:00
            Stats  : +1/-1 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/fedora-repos/c/d501e7f0a46db16be88a46d0bba981d7f4684c09?branch=f45

            Log:
            Remove spurious space ` ` in RPM-GPG-KEY-fedora-37-primary

gpg accepts this, whereas librpm's bespoke PGP code does not.
I didn't look at the specification but I doubt it allows extra
whitespace.

dnf uses the gpg APIs to import and canonicalize keys before passing
them to librpm.  gpg happily accepts the extra whitespace.

librpm has a bespoke PGP parser which rejects this.

Fixes https://github.com/rpm-software-management/libdnf/issues/1320

---
diff --git a/RPM-GPG-KEY-fedora-37-primary b/RPM-GPG-KEY-fedora-37-primary
index 71fc128..8ed5fff 100644
--- a/RPM-GPG-KEY-fedora-37-primary
+++ b/RPM-GPG-KEY-fedora-37-primary
@@ -1,5 +1,5 @@
 -----BEGIN PGP PUBLIC KEY BLOCK-----
- 
+
 mQINBGESvNwBEAC7HsCDTlugVeDSMFX6aW3zAPFMfvBssNj+89fdmbxcI9t7UY6f
 HvkkGziUET8e+9jB8R2/wXQCGOw1J+sfmwO4aN0LdVQjhKvVNj+F5jWt3m5FAIBa
 OTWS6Kvqw2ECTpH7fD86541eK3BuCni6d5U3PCd73t976FcUmpQ/1AthqMksM0Jz

                 reply	other threads:[~2026-08-10  9:41 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=178635487666.1.8746471665101878948.rpms-fedora-repos-d501e7f0a46d@fedoraproject.org \
    --to=walters@verbum.org \
    --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