kparal added a new comment to an issue you are following:
``
Ah, that's not going to be in the final PR :-) That's just a way to ensure that
the experimental package from my COPR always beats Rawhide package.
That's a trailing space fix, inconsequential. That got added automatically when I
edited the file, doesn't need to be part of the final PR.
I'd say leave the 32 key there as a link to rawhide for now?
Do you mean this?
```
rename from RPM-GPG-KEY-fedora-32-primary
rename to RPM-GPG-KEY-fedora-rawhide-primary
```
In my experience, the GPG key gets looked up according to `$releasever`, so it has to be
named `fedora-rawhide-primary` now. Of course we can create a symlink `fedora-32-primary
-> fedora-rawhide-primary`. But because this change is intended just for Rawhide (and
not older releases), I assumed this wasn't necessary. But thinking more about it (e.g.
regarding upgrades) it might be safer to have both. I'll add the symlink (and also
keep both entries in `archmap`).
Finally, should we put in a f32 change for this? It might be good to
get more visibility before making the change...
There was a devel discussion about it, but not many people participated. I guess it might
be a good idea to have a Change proposal for this. Does anyone from Releng/Infra want to
create it, or should I? In the latter case, who'd want to co-own the Change with me?
Have you done any testing with it and do things generally look ok?
I don't run a Rawhide system long-term anywhere, so I performed testing only in a VM.
It was nothing extensive, just making sure the DNF and repos work as expected. Now that
F31 is properly branched, I can perform some more testing (switching from Rawhide to
Branched and back).
What would be the best time to make this live in Rawhide? Very soon, so that people can
experiment with Branched interactions as well, or once F31 is stable, so that we don't
introduce Rawhide-related issues during F31 stabilization? Even after reading the Change
policy, I'm unclear whether this needs to wait for FESCo approval before putting it
into Rawhide, whether I can already propose changes for F32 and whether gets approved soon
(or just after F31 is out).
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7445