Hi! I could not find a safe way to upgrade also this time. I found update F32 [1], but not corresponding F31 just adding new key. I am missing update similar to [2], just for F31 that once was Rawhide. It should be version 31-0.5 I found and reopened one old bug [3]. I do not think this is just second time. On 8/19/19 11:32 PM, Kevin Fenzi wrote: > So, a few things to note: > > * fedora-repos was updated for rawhide, however, unfortunately, It had > two extra spaces on the first line... " " which made gpg consider it > invalid. This is likely the cause of any breakage with rawhide (mock, > containers, copr, etc). This has been fixed in the newest fedora-repos > package for f32/rawhide. > > * There is no f31 repo because we have not yet had a fedora 31 branched > compose finish. So, mirrormanager is pointing people to rawhide. This is > likely the cause of all problems related to f31. I think this is a major point. I could not find update with fedora-repos-31-0.5 signed. Instead, there is 32-0.1 served both by f31 updates and rawhide repo. I think there must be first updated GPG keys N, which increases just minor version, not a major one. Major version should be increased only after branching. Unless I am mistaken, rawhide served me 32-0.1 signed by key contained inside. Okay, I had rawhide repo enabled. But even $ dnf --repo=updates --releasever=31 upgrade fedora-gpg-keys did not offer different version. What was worse, both were signed by the same F32 key. > > * Finally, updates are queued for f29/30/31 to add the f32 key. This > shouldn't really be that big a deal unless you are running one of those > and want to update to rawhide, or is there other cases here? > > I think the first 2 items are the ones causing problems, and the third > is not so urgent as them. Sure, we can add it to the schedule and do it > in advance, but the other things are the things to really avoid next time. > > kevin > > > > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > 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@xxxxxxxxxxxxxxxxxxxxxxx > 1. https://bodhi.fedoraproject.org/updates/FEDORA-2019-12c2cfd23a 2. https://bodhi.fedoraproject.org/updates/FEDORA-2019-7ac161b9d7 3. https://bugzilla.redhat.com/show_bug.cgi?id=1489628 -- Petr Menšík Software Engineer Red Hat, http://www.redhat.com/ email: pemensik@xxxxxxxxxx PGP: 65C6C973
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
