search

rpm-software-management / mock

Mock is a tool for a reproducible build of RPM packages.
GNU General Public License v2.0
376 stars 220 forks source link

configs: Rawhide to accept GPG key from future Fedora Rawhide+1 #1342

Open praiskup opened 4 months ago

praiskup commented 4 months ago

Fixes: #1338

praiskup commented 4 months ago

This time, F42 key was generated on 2024-02-12. The plan was to have it about ~14 days before signing rawhide with f41 key, which IMO happened (the mass rebuild took a bit more time). Not sure. Mock-core-configs with branched F40 2024-02-14. Which was admittedly too late, it would be nice to do that 14 days earlier next time.

xsuchy commented 4 months ago

I have to say that I am not happy for this PR. IMO this will bring a new issue when we submit new config earlier than before branching (missing key). I would rather resolve it by dynamically using number for rawhide. Likely using python-fedora-distro-aliases https://github.com/rpm-software-management/fedora-distro-aliases In such case we would not need to touch rawhide config after branching at all!

praiskup commented 4 months ago

"fedora-repos update with the new keys is available in updates-testing" is though something different, I think that we should have a new entry in the F41 schedule like

Generate Fedora N+2 key and ship in fedora-repos

Somewhere in the Fedora 41 schedule. To have a guidance that assures everything works.

praiskup commented 4 months ago

I have to say that I am not happy for this PR. IMO this will bring a new issue when we submit new config earlier than before branching (missing key).

If we can get a new step into the Fedora release schedule, then this problem would be non-existing.

I would rather resolve it by dynamically using number for rawhide. Likely using python-fedora-distro-aliases https://github.com/rpm-software-management/fedora-distro-aliases In such case we would not need to touch rawhide config after branching at all!

This is being tracked here #1328 - though :-/ it's going to be a big change in the way mock and core-configs behave.