On 11/03/19 15:01 +0100, Jan Pokorný wrote: > On 11/03/19 12:31 +0100, Vít Ondruch wrote: >> Can somebody please enlighten me, how to update Rawhide after branching >> and not using --nogpgcheck? > > Good question; have observed this over several (if not all since > to-be-f26 based Rawhide) jumps like that, and always have solved this > inconvenience by hand and moved on. > > GPG signatures related must-do consequence of branching for those > using mock with the branched + Rawhide targets is also to update > mock-core-configs, which is currently also not very straightforward > and could perhaps be handled more gracefully: > https://bugzilla.redhat.com/show_bug.cgi?id=1686869 Actually, fedora:rawhide container from Docker Hub (in CI scenario here) is affected with this problem as well (cannot update with the new-key-signed f30/f31 packages because of this, making the CI procedure fail[*]). Should not at least the "official container images" follow the branching point automatically and promptly to prevent GPG signature imposed disruptions ASAP? [*] https://gitlab.com/poki/pacemaker/-/jobs/175445117 -- Jan (Poki)
Attachment:
pgpl7VpS2hoM0.pgp
Description: PGP signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
