
Originally Posted by
else_where
Yeah, I get that too. The fix is to select the "don't install policykit-kde" option. The basic problem is that the KDE 4.0 package for policykit-kde has a newer release-number than the 4.1 package, so Yast automatically selects that one, which forces a downgrade of the KDE 4.1 packages to meet the dependencies. It's a bug that should be addressed soon.
It's safe to ignore it if you don't need it. If you do need it, then the work around in Yast is to force-select the KDE/Factory version by using the appropriate tab after selecting policykit-kde in the main screen. It's a kludge, but only a corner case unless you need it.
Hope this helps...
Cheers,
KV
Bookmarks