Description of problem: virt-manager 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. (Note that virt-manager is not included on the current KDE spin.) Version-Release number of selected component (if applicable): virt-manager-0:0.6.1-2.fc11 How reproducible: Always Steps to Reproduce: 1. repoquery --repoid=rawhide --whatrequires PolicyKit-gnome Actual results: virt-manager requires PolicyKit-gnome. Expected results: virt-manager does not require PolicyKit-gnome. Additional info: Maybe a common Provides in both PolicyKit-gnome and PolicyKit-kde is needed?
Looks to me like we can just require PolicyKit >= 0.7: http://hg.et.redhat.com/cgi-bin/hg-virt.cgi/applications/virt-manager--devel/file/8176c489cd55/src/virtManager/connection.py#l309 i.e. since PolicyKit 0.7 we use org.freedesktop.PolicyKit.AuthenticationAgent which can be implemented by either PolicyKit-gnome or PolicyKit-kde, rather than directly using org.gnome.PolicyKit
Yeah, there's no reason for us to depend on PolicyKit-gnome directly anymore in Fedora.
In Rawhide, both PolicyKit-gnome and PolicyKit-kde now have: Provides: PolicyKit-authentication-agent so you can require this instead of PolicyKit-gnome.
Okay, this is in virt-manager-0.6.1-4.fc11. Closing