Il 01/05/21 19:49, Kevin Fenzi ha scritto:
On Sat, May 01, 2021 at 11:42:52AM +0200, Germano Massullo wrote:
> Il 30/04/21 18:33, Kevin Fenzi ha scritto:
>> On Fri, Apr 30, 2021 at 02:19:31PM +0200, Germano Massullo wrote:
>>> After running
>>> dnf system-upgrade download --releasever=34
>>> and downloading all files, I got the following warning
>>> warning:
>>>
/var/lib/dnf/system-upgrade/fedora-e21c25ac3662d294/packages/fstrm-0.6.0-4.fc34.x86_64.rpm:
>>> Header V4 RSA/SHA256 Signature, ID key 45719a39: NOKEY
>>>
>>> Why this package does not have a key?
>> That is in fact the f34 key and the package is signed with it.
>>
>> You don't have that key in your rpmdb (which is why it says NOKEY).
> Mmh why it says that only for that package?
Don't know. ;( Do you still have that file? Or it's gone with the
upgrade?
What file?
>> There was a fedora-release for f33/f32 that had this key in
it, if you
>> updated to that it should have been able to correctly import it.
> I always upgrade from N to N+1 Fedora versions
>
>> Hard to say whats going on without more info.
>> What version is there? what version of fedora-release do you have
>> installed?
> From dnf system upgrade logs I see a
> fedora-release-common-33-4.noarch
Yeah, that should definitely have the key in it and if the rest worked I
don't see why that one package would be singled out...
Perhaps file a bug on dnf system-upgrade plugin and see if they can
figure it out?
Ah I found out this my old bugreport
https://bugzilla.redhat.com/show_bug.cgi?id=1286652
which leads to
"Feature request: make clear RPM to trigger key import is signed"
https://bugzilla.redhat.com/show_bug.cgi?id=1293882
that is a bugreport where people already started to work on it years ago