public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/fedora-repos] f45: Allow to use newer GPG keys, so Rawhide can be updated after branch.
Date: Mon, 10 Aug 2026 09:40:53 GMT	[thread overview]
Message-ID: <178635485347.1.3961232984112405512.rpms-fedora-repos-7fe18642e830@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/fedora-repos
            Branch : f45
            Commit : 7fe18642e83021bdb27698512d2401ba54a6e9ac
            Author : Vít Ondruch <vondruch@redhat.com>
            Date   : 2019-04-24T10:28:24+02:00
            Stats  : +5/-2 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/fedora-repos/c/7fe18642e83021bdb27698512d2401ba54a6e9ac?branch=f45

            Log:
            Allow to use newer GPG keys, so Rawhide can be updated after branch.

Currently, the GPG keys have to be updated together with repositories.
But there is no strong relationship between them. After branching, there
has has to be possible to update GPG keys independently, otherwise, it
is not possible to keep updating Rawhide without usign --nogpgcheck or
different "cheating".

Original discussion of fedora-devel:

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/MFX2JDVANNEW7LWWIBBLYCN6DEPWHSXF/

Signed-off-by: Vít Ondruch <vondruch@redhat.com>

---
diff --git a/fedora-repos.spec b/fedora-repos.spec
index 0525c99..a82e2a2 100644
--- a/fedora-repos.spec
+++ b/fedora-repos.spec
@@ -1,14 +1,14 @@
 Summary:        Fedora package repositories
 Name:           fedora-repos
 Version:        31
-Release:        0.2%{?_module_build:%{?dist}}
+Release:        0.3%{?_module_build:%{?dist}}
 License:        MIT
 URL:            https://fedoraproject.org/
 
 Provides:       fedora-repos(%{version})
 Requires:       system-release(%{version})
 Requires:       fedora-repos-rawhide = %{version}-%{release}
-Requires:       fedora-gpg-keys = %{version}-%{release}
+Requires:       fedora-gpg-keys >= %{version}-%{release}
 Obsoletes:      fedora-repos-anaconda < 22-0.3
 Obsoletes:      fedora-repos-modular < 29-0.6
 Provides:       fedora-repos-modular = %{version}-%{release}
@@ -166,6 +166,9 @@ install -m 644 %{_sourcedir}/fedora.conf $RPM_BUILD_ROOT/etc/ostree/remotes.d/
 /etc/ostree/remotes.d/fedora.conf
 
 %changelog
+* Tue Mar 12 2019 Vít Ondruch <vondruch@redhat.com> - 31-0.3
+- Allow to use newer GPG keys, so Rawhide can be updated after branch.
+
 * Thu Mar 07 2019 Sinny Kumari <skumari@redhat.com> - 31-0.2
 - Create fedora-repos-ostree sub-package
 

                 reply	other threads:[~2026-08-10  9:40 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=178635485347.1.3961232984112405512.rpms-fedora-repos-7fe18642e830@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