Description of problem:
Updating a Koji based system today has pulled in a number of KDE packages which are not only undesirable on this pure GNOME system but, moreover, appear to be not even required. Executing 'yum update' returns the following schedule:
Installing for dependencies:
'yum remove constantine-backgrounds-kde ..' appending all packages listed above allows to remove them altogether without interfering with the rest of the system which makes one wonder why they got pulled in in the first place.
Before, only the following KDE packages were installed after selecting language support for French and Spanish during system install:
PolicyKit-kde [obsoleted by polkit]
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Execute 'yum update' koji system on 2009-09-15 at 18:56 MEST.
A significant number of KDE packages gets installed without any obvious requirement.
Only required packages get installed in addition to updated packages.
1. what does a ' koji-based system' mean?
2. can you include the full output of: yum -d 7 update so we can see what pkgs are being updated that are pulling in kde requirements?
Created attachment 361122 [details]
Output of 'yum -d 7 update' after downgrading to (obsolete) package PolicyKit-kde
1. This means that a file fedora-koji.repo is present in /etc/yum.repos.d,
all other repos being disabled, and its content reading
name= koji - Koji Development Packages
2. It seems as if the culprit was PolicyKit-kde [full log attached] which
became evident after forcing the downgrade to (obsolete) package
PolicyKit-kde and of related packages.
kdebase-workspace also replaces polkit-qt with the same effect.
so PolicyKit-kde is obsoleted by kdebase-workspace which is what is pulling in everything?
If so - then shouldn't this bug report go to the pkgers of those packages?
(In reply to comment #4)
Doesn't sound that stupid after all ..
Why did you have PolicyKit-kde and polkit-qt installed on a non-KDE system in the first place? This stuff was only dragged in by KDE (kdebase-workspace itself and kpackagekit), so it's normal that KDE is obsoleting it out.
(In reply to comment #6)
Looking at /root/install.log of the "rawhide" install, two entries are particularly interesting:
I had chosen language support for French and Spanish which triggered
even on a pure GNOME system. A further dependency for PolicyKit-kde led to
Now, the interesting point is that system-config-services-0.99.39-1.fc12.noarch requires PolicyKit-authentication-agent which is provided either by PolicyKit-kde or by PolicyKit-gnome. However, it is the former which got pulled in instead of the latter.
After installing PolicyKit-gnome-0.9.2-5.fc12.x86_64 and PolicyKit-gnome-libs-0.9.2-5.fc12.x86_64, PolicyKit-kde can actually be removed without complaint, likewise polkit-qt.
Btw, disabling the Koji branch and enabling the "rawhide" repository does not make any difference regarding the issue reported above.
I guess that's a Rawhide-only issue. F11 installs had PolicyKit-gnome dragged in by the GNOME comps group, so they shouldn't have received -kde on pure GNOME systems.
But anyway, if the consensus is that polkit should be what obsoletes PolicyKit-kde and polkit-qt, I can drop the Obsoletes from kdebase-workspace. (I just put them there for lack of a better place to put them.)
fwiw, PolicyKit-kde no longer exists on F-12 (or soon won't), problem solved.
Oh, the Obsoletes issue remains, sorry.
Kevin's suggestion in comment #9 about moving the Obsoletes make sense.
Talked out load (and with jreznik) in irc a bit, and I changed my mind. With a kde authenticator making a comeback in the not-too-distant future, doing the obsoletes outside of kde packaging and getting the versioning right and safe would be tricky.
So is this a WONTFIX?
Steven M. Parrish - KDE Triage Master
- PackageKit Triager
Fedora Bugzappers volunteer triage team
On Sep 25, 2009, I have performed another install from scratch from the "rawhide" tree similarly to the one preceding this bug report.
There are no '*kde*' installed anymore, not even the language related ones.
For system upgrades this might look different, but they are not supported for the transition from development snapshots to F12 anyway, and F11 did not have this problem either.
Well, then I'd say this is just part of the regular Rawhide pain and it's already fixed for current Rawhide installs, so closing.