Hi guys, I’m trying to upgrade a box from F32 to F34. I originally installed the full workstation release but over the years I have been getting rid of stuff I don’t want so it is a bit different from a vanilla install.
I get some errors regarding PackageKit and I don’t know whether the --skip-broken workaround is ok in my case or not:
root@box:~# dnf system-upgrade download --releasever=34
Before you continue ensure that your system is fully upgraded by running “dnf --refresh upgrade”. Do you want to continue [y/N]: y
Fedora 34 openh264 (From Cisco) - x86_64 221 B/s | 989 B 00:04
Fedora Modular 34 - x86_64 33 kB/s | 26 kB 00:00
Fedora Modular 34 - x86_64 - Updates 46 kB/s | 24 kB 00:00
Fedora 34 - x86_64 - Updates 49 kB/s | 25 kB 00:00
Fedora 34 - x86_64 272 kB/s | 26 kB 00:00
google-chrome 23 kB/s | 1.3 kB 00:00
RPM Fusion for Fedora 34 - Free - Updates 80 kB/s | 7.1 kB 00:00
RPM Fusion for Fedora 34 - Free 18 kB/s | 7.0 kB 00:00
RPM Fusion for Fedora 34 - Nonfree - Updates 55 kB/s | 6.6 kB 00:00
RPM Fusion for Fedora 34 - Nonfree 17 kB/s | 6.5 kB 00:00
No match for group package “dnf-yum”
No match for group package “gnome-documents”
No match for group package “fedora-user-agent-chrome”
No match for group package “kexec-tools-anaconda-addon”
No match for group package “totem-nautilus”
Problem: package PackageKit-gtk3-module-1.1.13-3.fc32.i686 requires PackageKit-glib(x86-32) = 1.1.13-3.fc32, but none of the providers can be installed
PackageKit-glib-1.1.13-3.fc32.i686 does not belong to a distupgrade repository
problem with installed package PackageKit-gtk3-module-1.1.13-3.fc32.i686
(try to add ‘–skip-broken’ to skip uninstallable packages)
IMO, Skip broken is not a good option to use when doing a full system upgrade. It is much better to do the full update as instructed then once dnf is happy that way do the system upgrade with an already stable environment.
You can also remove the package it complains about, do the system-upgrade, then reinstall that package if needed so it matched the new version.
I suspect you cannot do a routine dnf update on the current system since F32 is now EOL for support. I do know the old repo is archived but I have not kept track of where, so you might need to ask about that specifically. The easiest fix would be to remove the package it is complaining about then reinstall after the upgrade is complete.
You might want to keep in mind that approximately 1 month after a new version is officially released the older version (2 steps back) goes EOL. Thus F32 went EOL in May.
Thank you. I keep current on dnf upgrade --refresh and even so the upgrade to F34 seems to be dependent on getting past the error message.
The problem with removing any package seems to be that everything depends on everything else. It’s difficult to remove this one without causing a cascade. Is it possible to ignore/override the warning and deal with it after the system is upgraded?