Bug 5693

Summary:	Wrong Key in Release?
Product:	Infrastructure	Reporter:	Robert Spigler <RobertSpigler>
Component:	Repo	Assignee:	Nicolas Chauvet <kwizart>
Status:	RESOLVED INVALID
Severity:	normal	CC:	lxtnow, matthias, sergio
Priority:	P1
Version:	NA
Hardware:	x86_64
OS:	GNU/Linux
namespace:

Description Robert Spigler 2020-07-06 20:32:50 CEST

Trying to upgrade Fedora 30 to Fedora 32; I am getting a `GPG check FAILED` error. 

Log:

warning: /var/cache/dnf/rpmfusion-free-b06e117020f7383b/packages/rpmfusion-free-obsolete-packages-32-2.fc32.noarch.rpm: Header V3 RSA/SHA1 Signature, key ID 100bcd92: NOKEY
RPM Fusion for Fedora 32 - Free 1.1 MB/s | 1.7 kB 00:00
Importing GPG key 0xC481937A:
Userid : "RPM Fusion free repository for Fedora (31) rpmfusion-buildsys@lists.rpmfusion.org"
Fingerprint: 59A7 FE07 F664 C1B2 7687 C5D2 6DEE F051 C481 937A
From : /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-32
Is this ok [y/N]: y
Key imported successfully
Import of key(s) didn't help, wrong key(s)?

Filename is Fedora-32, but key descriptions is Fedora (31).

Tried updating first with `sudo dnf upgrade --refresh` to see if there was a fix, but my system was up to date.

`gpg /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-32` shows that I do indeed have the Fedora 31 RPMFusion Key.

Robert

Comment 1 Nicolas Chauvet 2020-07-06 20:50:03 CEST

Which method are you using to upgrade ?
Are you upgrading from a fully updated f30 ? 
which rpmfusion-free-release package do you have ? Do you have the rpmfusion "updates" repository enabled during upgrade ?

Comment 2 Robert Spigler 2020-07-06 23:00:01 CEST

I am using Qubes, so I imagine it is a bit different, but I do not think this is a Qubes specific issue. (I have filed with Qubes as well however: https://github.com/QubesOS/qubes-issues/issues/5936).

I am upgrading the Fedora TemplateVM, and following their detailed documentation (https://www.qubes-os.org/doc/template/fedora/upgrade/)

1. Ensure the existing template is not running.
2. Clone the existing template and start a terminal in the new template.
3. Attempt the upgrade process in the new template.

Before cloning, I make sure the Fedora 30 TemplateVM is fully up to date:

`sudo dnf upgrade --refresh`.  There are no update to do.

To upgrade, it involves running:

`sudo dnf clean all`
`sudo dnf --releasever=<new> distro-sync --best --allowerasing`

I have imported the new signing keys:

97A1 AE57 C3A2 372C CA3A 4ABA 6C13 026D 12C9 44D0
59A7 FE07 F664 C1B2 7687 C5D2 6DEE F051 C481 937A



I guess I only had the rpmfusion-free repo enabled.  I enabled rpmfusion-free-rupdates by running `sudo dnf config-manager --add-repo /etc/yum.repos.d/rpmfusion-free-updates.repo`.

Re-running `sudo dnf upgrade --refresh` results in still no updates.  However, I still only see RPM Fusion for Fedora 30 - Free queried, no RPM Fusion For Fedora 30 - Free (updates) like I would have thought.

Comment 3 Robert Spigler 2020-07-07 02:53:04 CEST

Fixed.

It is because I need to use the command `--set-enabled`, not `--add-repo`

Comment 4 Sérgio Basto 2020-07-25 14:38:21 CEST

not a bug, per the last comment