|
Dne 20. 08. 19 v 18:40 Kevin Fenzi
napsal(a):
On 8/20/19 7:37 AM, Petr Mensik wrote: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.Yes, it is that version, but there is not any compose that it exists in yet.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.yes, because both f31 and f32 are currently pointing to f32 (rawhide). If we had a f31 compose you would not have hit this. You would update to the new f31 version and from there you could upgrade to f32 or stay on f31.
That is not completely true. The only possible way is to update
the `fedora-gpg-keys` first without anything else and that was the
reason for [1]. But since [1] did not landed in Fedora prior the
branch, there is no way to update Rawhide and keep everything
Rawhide and at the same time keep checking signatures all the
time. IOW prior branch, I had installed fedora-repos-31-0.2 together with fedora-gpg-keys-31-0.2. As long as there was no F31 compose, there was available fedora-repos-32-0.2 together with fedora-gpg-keys-32-0.2 (or 0.1, it does not really matter), but those were not possible to install, because they are signed by F32 GPG key, which is not available on my system yet. The fedora-repos-31-0.5 is the first post branch package signed with the key on my system. This allows me to install fedora-gpg-keys-31-0.5 but at the same time it changes the configuration of /etc/yum.repos.d/fedora{,-rawhide}.repo making the system F31 instead of Rawhide. And this is wrong. But it should be better next time, because [1] finally landed. It allows to update fedora-gpg-keys without updating fedora-repos. That means it should be possible to get the new Rawhide keys and then keep updating from Rawhide repository.
Vít
kevin |
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
