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:
>> 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 key
They 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
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"
>> this package was not probably signed, because this directory is empty:
> Yeah, no longer shipped packages have their signed packages removed
> after a while to save space. You just want any newer one there.
> 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
Last metadata expiration check: 0:01:12 ago on Tue Mar 12 12:12:22 2019.
Problem: cannot install both fedora-gpg-keys-30-0.5.noarch and
- 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
- problem with installed package fedora-repos-30-0.2.noarch
Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
@commandline 102 k
Skip 1 Package
Nothing to do.
Which is not what you expect?
Try again with --enablerepo=fedora ? You need the base repo not just