This is the time of the year again and I must say that the situation
improved. The process was:
~~~
$ sudo dnf update fedora-gpg-keys
$ sudo dnf update fedora-repos --release 33
~~~
Where for the second command, you have to confirm the GPG key import.
Please note that the `--release 33` has to be specified, because while
the fedora-rawhide repos points to a `rawhide` mirror:
~~~
metalink=https://mirrors.fedoraproject.org/metalink?repo=rawhide&arch...
~~~
The GPG key refers to `$releasever`
~~~
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
~~~
This is discussed in
https://pagure.io/releng/issue/7445 AFAIK.
Vít
Dne 19. 08. 19 v 10:50 Zbigniew Jędrzejewski-Szmek napsal(a):
This seems to repeat every 6 months: rawhide mock is broken on
stable
Fedora, people are scrambling to install the right gpg keys, dnf reports
unsigned packages.
Looking at
https://bodhi.fedoraproject.org/updates/?packages=fedora-repos,
there is still no F30 package with the right keys.
Can we *please* send out the FN+1 and FN+2 keys a month before branching,
to *all* releases of Fedora, so we can avoid this pointless scramble?
Zbyszek
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org