kevin added a new comment to an issue you are following:
``
I've updated fedora-repos to include both fedora-rawhide and fedora-32 GPG key
files.
This might need some additional thought from the Releng team. I'm not sure I fully
understand how GPG keys are maintained and used. The major difference with this patch is
that the Rawhide key is no longer dynamically named
(RPM-GPG-KEY-fedora-$releasever-primary), but it is static
(RPM-GPG-KEY-fedora-rawhide-primary). Of course symlinks can be used, the file can be
regenerated periodically, etc. Or the Rawhide key can be the same key forever. So somebody
knowledgeable needs to say whether I should adjust the PR somehow or not. Also, some keys
are distributed in distribution-gpg-keys, and I don't know whether to adjust it in
some way as well.
I don't think we want to keep the same rawhide key forever, I think it's still
good to move to a new one at the branching point.
Question: Does rpm/dnf handle the case where the key file is named the same, but changes
content? ie, say we land this soon and when we branch f32 off we switch rawhide to a new
key with the same filename. Does dnf reimport it? say it's already imported and
fail?
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7445