msuchy reported a new issue against the project: `releng` that you are following:
We have signed rawhides now. Great. So I (as mock maintainer) am going to enable gpgcheck
in rawhide configs. But there will be problem around branching.
When we branch F26, you will create new gpg key for F27 and rawhide will be signed by F27
keys. So until people update mock (which may take 2 weeks) on EPEL. They will have invalid
GPG key for rawhide and therefore mock rawhide builds will fail for them.
There is one option as you can put in yum/dnf config more than one GPG keys. E.g.:100:
But which one as F27 keys does not exists yet. And DNF will complain on nonexistent file
(just tested that).
So the question is: what to put in mock config so
1) DNF in mock check gpgkey on rawhide
2) it does not cause problem to users during branching period
3) ideally it does not change rawhide mock config every release (so update does not create
To reply, visit the link below or just reply to this email