I successfully upgraded from Fedora Silverblue 38 to 39. I have the issue that Gnome software center constantly offers and (attempts) to install glibc-langpack-sl 2.38-7.fc39 => 2.38-10.fc39, but the package doesn’t get installed.
Any suggestion?
I successfully upgraded from Fedora Silverblue 38 to 39. I have the issue that Gnome software center constantly offers and (attempts) to install glibc-langpack-sl 2.38-7.fc39 => 2.38-10.fc39, but the package doesn’t get installed.
Any suggestion?
Does rpm-ostree upgrade
succeed? If not, please share the output.
I get the following output:
2 metadata, 0 content objects fetched; 788 B transferred in 2 seconds; 0 bajtov content written
Checking out tree b34773f... done
Enabled rpm-md repositories: fedora-cisco-openh264 updates fedora copr:copr.fedorainfracloud.org:phracek:PyCharm updates-archive
Importing rpm-md... done
rpm-md repo 'fedora-cisco-openh264' (cached); generated: 2023-03-14T10:57:01Z solvables: 4
rpm-md repo 'updates' (cached); generated: 2023-11-07T01:31:21Z solvables: 9604
rpm-md repo 'fedora' (cached); generated: 2023-11-03T02:50:25Z solvables: 70825
rpm-md repo 'copr:copr.fedorainfracloud.org:phracek:PyCharm' (cached); generated: 2023-08-10T15:35:19Z solvables: 5
rpm-md repo 'updates-archive' (cached); generated: 2023-11-07T02:12:54Z solvables: 7726
Resolving dependencies... done
No upgrade available.
The update still shows up after a reboot in Gnome software center.
I have the same issue but with 3 packages - Network manager and a couple for vim.
I think it’s something to do with the versions in the F39 repos needing to get updated; should clear up in a few days. I remember something similar happening going from F37->F38.
I bet you see the troublesome package when running rpm-ostree upgrade --preview
. Note the warning and link to the github issue regarding the --preview
flag. I think that’s what Gnome Software is using.
$ rpm-ostree upgrade --preview
note: automatic updates (stage) are enabled
1 metadata, 0 content objects fetched; 592 B transferred in 1 seconds; 0 bytes content written
Enabled rpm-md repositories: fedora-cisco-openh264 updates fedora updates-archive
Updating metadata for 'fedora-cisco-openh264'... done
Updating metadata for 'updates'... done
Updating metadata for 'fedora'... done
Updating metadata for 'updates-archive'... done
Importing rpm-md... done
rpm-md repo 'fedora-cisco-openh264'; generated: 2023-03-14T10:57:01Z solvables: 4
rpm-md repo 'updates'; generated: 2023-11-07T01:31:21Z solvables: 9604
rpm-md repo 'fedora'; generated: 2023-11-03T02:50:25Z solvables: 70825
rpm-md repo 'updates-archive'; generated: 2023-11-07T02:12:54Z solvables: 7726
Note: --check and --preview may be unreliable. See https://github.com/coreos/rpm-ostree/issues/1579
AvailableUpdate:
Upgraded: NetworkManager-team 1:1.44.0-1.fc39 -> 1:1.44.2-1.fc39
vim-common 2:9.0.1927-1.fc39 -> 2:9.0.2081-1.fc39
vim-enhanced 2:9.0.1927-1.fc39 -> 2:9.0.2081-1.fc39
$ rpm-ostree upgrade
note: automatic updates (stage) are enabled
2 metadata, 0 content objects fetched; 788 B transferred in 1 seconds; 0 bytes content written
Checking out tree 33546bf... done
Enabled rpm-md repositories: fedora-cisco-openh264 updates fedora updates-archive
Updating metadata for 'fedora-cisco-openh264'... done
Updating metadata for 'updates'... done
Updating metadata for 'fedora'... done
Updating metadata for 'updates-archive'... done
Importing rpm-md... done
rpm-md repo 'fedora-cisco-openh264'; generated: 2023-03-14T10:57:01Z solvables: 4
rpm-md repo 'updates'; generated: 2023-11-07T01:31:21Z solvables: 9604
rpm-md repo 'fedora'; generated: 2023-11-03T02:50:25Z solvables: 70825
rpm-md repo 'updates-archive'; generated: 2023-11-07T02:12:54Z solvables: 7726
Resolving dependencies... done
No upgrade available.
Exactly, when running rpm-ostree upgrade --preview, I get (I post just the final part of the output):
AvailableUpdate:
Upgraded: glibc-langpack-sl 2.38-7.fc39 -> 2.38-10.fc39
The OS runs great, this is just a small issue.
Looks like No new stable compose since 39.20231103.n.0 · Issue #502 · fedora-silverblue/issue-tracker · GitHub and should be fixed now.
It got resolved yesterday evening for me.