On Rocky 9.5 I uninstalled PackageKit.
Rocky 9.6 has put it back!
How/When does RHEL/Rocky/DNF decide to install a package that was not installed on the previous version?
Logically, a new version for some package, which you had installed, has now explicit dependency that pulls in the other package (PackageKit).
Command like “dnf rm packagekit” should list the other packages that reguire the package that you are about to remove.
If a package is magically showing back up, it’s because it’s a weak dependency (usually a recommended package) of another.
These flat out require PackageKit.
[root@router ~]# dnf repoquery -q --whatrequires PackageKit
PackageKit-command-not-found-0:1.2.6-1.el9.aarch64
cockpit-packagekit-0:334.1-1.el9_6.noarch
plasma-discover-packagekit-0:5.27.11-1.el9.aarch64
plasma-pk-updates-1:0.3.2-13.el9.aarch64
These “recommend” PackageKit, meaning it’s a weak dep and if dnf finds PackageKit, it will attempt to install it.
[root@router ~]# dnf repoquery -q --whatrecommends PackageKit
PackageKit-Qt5-0:1.1.1-2.el9.aarch64
cockpit-system-0:334.1-1.el9_6.noarch
gnome-software-0:45.3-3.el9.aarch64
Either exclude the package in your repo files or use --setopt=install_weak_deps=False when running dnf.
Thanks for the updates.
Of all the packages listed above, the only one I have is ‘cockpit-system.noarch’. Maybe that the one causing the issue. I don’t even use cockpit.
But I also noticed I have
PackageKit-glib.x86_64
PackageKit-gstreamer-plugin.x86_64
PackageKit-gtk3-module.x86_64
I have no idea what they are for; I don’t think they are dependencies, as there was no warning about needing to remove them…