Description of problem: system-config-services has a hardcoded dependency on PolicyKit-gnome. Is this really necessary? In the KDE spin, we would like to ship PolicyKit-kde instead of PolicyKit-gnome. PolicyKit-kde also implements the org.freedesktop.PolicyKit.AuthenticationAgent service. system-config-services is included on the current KDE spin. gnome-mount and system-config-services are the packages actually dragging PolicyKit-gnome onto the KDE spin. Version-Release number of selected component (if applicable): system-config-services-0:0.99.31-1.fc11 How reproducible: Always Steps to Reproduce: 1. repoquery --repoid=rawhide --whatrequires PolicyKit-gnome Actual results: system-config-services requires PolicyKit-gnome. Expected results: system-config-services does not require PolicyKit-gnome. Additional info: Maybe a common Provides in both PolicyKit-gnome and PolicyKit-kde is needed?
> Additional info: > Maybe a common Provides in both PolicyKit-gnome and PolicyKit-kde is needed? I think so. Could you take care of that? This virtual dependency could be "dbus(session:org.freedesktop.PolicyKit.AuthenticationAgent)". BTW: what happens when both PolicyKit-gnome and -kde packages are installed? Which one gets used if something accesses the org.freedesktop.PolicyKit.AuthenticationAgent bus name?
In Rawhide, both PolicyKit-gnome and PolicyKit-kde now have: Provides: PolicyKit-authentication-agent so you can require this instead of PolicyKit-gnome.
As for coexistence of both, see bug 484945 - hopefully we can also get that sorted out by F11, but fixing the Requires allows us to ship only PolicyKit-kde on the KDE spin and thus also works around that issue.
Fixed in system-config-services-0.99.32-1.fc11 which is building right now.