|
Ok, so the process which worked for me was:
~~~ $ sudo dnf update https://kojipkgs.fedoraproject.org/packages/fedora-repos/30/0.5/data/signed/cfc659b9/noarch/fedora-{gpg-keys,repos{,-rawhide}}-30-0.5.noarch.rpm
$ sudo dnf update --enablerepo=rawhide fedora-gpg-keys --release
31 ~~~
But what I really hate about is that after the first step, my
system becomes F30. Yes, the other step changes it back to
Rawhide, but in the meantime, all the repos I had disabled (such
as rawhide-modular) are enabled again, because there is
unnecessary fiddling with repositories. I submitted https://src.fedoraproject.org/rpms/fedora-repos/pull-request/29, which would enable the process to simplify and avoid the issues with the repo files to either:
~~~ $ sudo dnf update
https://kojipkgs.fedoraproject.org/packages/fedora-repos/30/0.5/data/signed/cfc659b9/noarch/fedora-gpg-keys-30-0.5.noarch.rpm ~~~
or even to:
~~~ $ sudo dnf update --disablerepo=* --enablerepo=updates{,-testing}
fedora-gpg-keys ~~~
I have not tested the latter. I wish the PR was merged, because the strict relation between repos and gpg-keys serves no purpose IMO.
Vít
Dne 12. 03. 19 v 19:53 Kevin Fenzi
napsal(a):
On 3/12/19 4:14 AM, Vít Ondruch wrote:Dne 11. 03. 19 v 19:29 Kevin Fenzi napsal(a):On 3/11/19 4:31 AM, Vít Ondruch wrote:Hi, Can somebody please enlighten me, how to update Rawhide after branching and not using --nogpgcheck?Can you expand on the case here? What should happen is: * branching * f30 repos gets the f31 keyThey got the f31 key in -0.4, but the *signed* package with this key without subsequent changes to the repositories done in -0.5 is not available anywhere.Thats due to compose issues. A compose completed last night so this should be there now?* you update your f30-repos * you jump to rawhide and dnf just imports the key. How did you get on rawhide?It seems that Rawhide keys were added in fedora-repos-30-0.4. So this is the package which is still "rawhide" package and has "f31" keys. But this package was not probably signed, because this directory is empty: https://kojipkgs.fedoraproject.org/packages/fedora-repos/30/0.4/data/signed/Yeah, no longer shipped packages have their signed packages removed after a while to save space. You just want any newer one there. https://kojipkgs.fedoraproject.org/packages/fedora-repos/30/0.5/data/signed/cfc659b9/ for example.I did this try 30-0.5 of course, but this is wrong, since installing this package makes F30 from my Rawhide, that is not what I want. May the the whole problem is, that fedora-gpg-keys has to be updated together with fedora-repos?The problem is that we are calling rawhide two things and have seperate config for it. Once we call it 'rawhide' instead of a number and use the same config as other branches I think most of these problems will go away.$ LC_ALL=C.UTF-8 sudo dnf update --disablerepo=rawhide --enablerepo=updates-testing --release 30 https://kojipkgs.fedoraproject.org/packages/fedora-repos/30/0.5/data/signed/cfc659b9/noarch/fedora-gpg-keys-30-0.5.noarch.rpm Last metadata expiration check: 0:01:12 ago on Tue Mar 12 12:12:22 2019. Dependencies resolved. Problem: cannot install both fedora-gpg-keys-30-0.5.noarch and fedora-gpg-keys-30-0.2.noarch - package fedora-repos-30-0.2.noarch requires fedora-gpg-keys = 30-0.2, but none of the providers can be installed - cannot install the best update candidate for package fedora-gpg-keys-30-0.2.noarch - problem with installed package fedora-repos-30-0.2.noarch ============================================================================================================================================================================================== Package Architecture Version Repository Size ============================================================================================================================================================================================== Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): fedora-gpg-keys noarch 30-0.5 @commandline 102 k Transaction Summary ============================================================================================================================================================================================== Skip 1 Package Nothing to do. Complete! ~~~ Which is not what you expect?Try again with --enablerepo=fedora ? You need the base repo not just updates-testing? 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://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
