Fedora Silverblue 40 rebase fails due to rpm GPG signature error in qt5-qtquickcontrols?

$ rpm-ostree rebase fedora:fedora/40/x86_64/silverblue
2 metadata, 0 content objects fetched; 788 B transferred in 4 seconds; 0 Bytes content written
Checking out tree 7d06768... done
Enabled rpm-md repositories: fedora rpmfusion-free fedora-cisco-openh264 updates rpmfusion-free-updates updates-archive
Importing rpm-md... done
rpm-md repo 'fedora' (cached); generated: 2024-04-19T08:53:31Z solvables: 74873
rpm-md repo 'rpmfusion-free' (cached); generated: 2024-04-20T12:11:51Z solvables: 422
rpm-md repo 'fedora-cisco-openh264' (cached); generated: 2023-12-11T14:43:50Z solvables: 4
rpm-md repo 'updates' (cached); generated: 2024-04-29T01:08:34Z solvables: 8720
rpm-md repo 'rpmfusion-free-updates' (cached); generated: 2024-04-26T21:25:38Z solvables: 18
rpm-md repo 'updates-archive' (cached); generated: 2024-04-29T01:21:28Z solvables: 6905
Resolving dependencies... done
Will download: 14 packages (16,0 MB)
Downloading from 'fedora'... done
Importing packages... done
error: importing RPMs: package qt5-qtquickcontrols-5.15.13-1.fc40.x86_64 cannot be verified and repo fedora is GPG enabled: /var/cache/rpm-ostree/repomd/fedora-40-x86_64/packages/qt5-qtquickcontrols-5.15.13-1.fc40.x86_64.rpm could not be verified.
/var/cache/rpm-ostree/repomd/fedora-40-x86_64/packages/qt5-qtquickcontrols-5.15.13-1.fc40.x86_64.rpm:  PRĂśFSUMME:  SIGNATURE:  NICHT OK

This has worked before (I am in a little cycle downgrading and upgrading due to testing things, so I wonder why I now get such a strange error for that one package. Also, strangely enough, it’s also reproducible…)

$ ls -la /var/cache/rpm-ostree/repomd/fedora-40-x86_64/packages/qt5-*                                         
-rw-r--r--. 1 root root 1774195 30. Apr 00:32 /var/cache/rpm-ostree/repomd/fedora-40-x86_64/packages/qt5-qtquickcontrols2-5.15.13-1.fc40.x86_64.rpm
-rw-r--r--. 1 root root  463097 30. Apr 00:32 /var/cache/rpm-ostree/repomd/fedora-40-x86_64/packages/qt5-qtquickcontrols-5.15.13-1.fc40.x86_64.rpm
-rw-r--r--. 1 root root  101882 30. Apr 00:32 /var/cache/rpm-ostree/repomd/fedora-40-x86_64/packages/qt5-qtwebchannel-5.15.13-1.fc40.x86_64.rpm
-rw-r--r--. 1 root root 3351855 30. Apr 00:32 /var/cache/rpm-ostree/repomd/fedora-40-x86_64/packages/qt5-qtwebengine-5.15.16-4.fc40.x86_64.rpm
-rw-r--r--. 1 root root   89183 30. Apr 00:32 /var/cache/rpm-ostree/repomd/fedora-40-x86_64/packages/qt5-qtwebsockets-5.15.13-1.fc40.x86_64.rpm
$ sha256sum /var/cache/rpm-ostree/repomd/fedora-40-x86_64/packages/qt5-qtquickcontrols-5.15.13-1.fc40.x86_64.rpm        
9fdef8d117b407ff7fd220d64762ad550a6afe34aa5cb3a06eb69e3850ddbdd9  /var/cache/rpm-ostree/repomd/fedora-40-x86_64/packages/qt5-qtquickcontrols-5.15.13-1.fc40.x86_64.rpm

System

$ rpm-ostree status -b                                
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
BootedDeployment:
â—Ź fedora:fedora/39/x86_64/silverblue
                  Version: 39.20240429.0 (2024-04-29T00:42:04Z)
               BaseCommit: 190f07d86271feae4848cb21c0bebc21572341b08365d36313b7052a54c1399e
             GPGSignature: Valid signature by E8F23996F23218640CB44CBE75CF5AC418B8E74C
          LayeredPackages: ***

Lösch mal den Cache und guck dass Du nach den neuen/aktuellen Prüfsummen gefragt wirst.

“Clear the cache and see that you are asked for the new/current checksums.”

rpm-ostree --help
Usage:
  rpm-ostree [OPTION…] COMMAND

Builtin Commands:
 cleanup                Clear cached/pending data

p.s.
Ich habe deinen anderen topic erst im nach hinein gesehen. Da hast Du ja den cleanup schon mal gebraucht. Wenn Du in den Versionen hoch und runter gehst musst du immer wieder raus putzen.

“I only saw your other topic afterwards. You already needed the cleanup. If you go up and down the versions you always have to clean them out.”

Ah okay, so you need to clear the rpm(? – or which?) cache after doing a rpm-ostree upgrade?
If so okay, how? (dnf is obviously not installed on atomic desktop’s.)

(English only is fine BTW.)

You can delete cached rpm repo metadata with

rpm-ostree cleanup -bm

or refresh metadata with

rpm-ostree refresh-md --force
1 Like

Okay great, that seems to work.

For reference, -bm seems to remove cached rpm repo metadata and -b seems to remove some temporary files:

rpm-ostree cleanup --help
Usage:
  rpm-ostree cleanup [OPTION…]

Clear cached/pending data

Help Options:
  -h, --help            Show help options

Application Options:
  --os=OSNAME           Operate on provided OSNAME
  -b, --base            Clear temporary files; will leave deployments unchanged
  -p, --pending         Remove pending deployment
  -r, --rollback        Remove rollback deployment
  -m, --repomd          Delete cached rpm repo metadata
  --sysroot=SYSROOT     Use system root SYSROOT (default: /)
  --peer                Force a peer-to-peer connection instead of using the system message bus
  --version             Print version information and exit
  -q, --quiet           Avoid printing most informational messages

But if that is needed, why does not -p (which, as you correctly noticed I needed to revert rpm-ostree reset) implicitly remove the cache etc.?

I think it is rare to encounter this error after running rpm-ostree cleanup -p. Perhaps something else triggers it? You may want to open a bug report on rpm-ostree GitHub page.

1 Like

Done in: