Red Hat Bugzilla – Bug 1260252
Spurious package sssd-common-1.13.0-2.fc22.x86_64 requires libldb(x86-64) = 1.1.20, but none of the providers can be installed message
Last modified: 2015-09-11 06:27:26 EDT
Created attachment 1070440 [details]
Description of problem:
Currently there is an issue with a kde update. I'm getting:
# dnf upgrade --best --debugsolver
Repository rawhide has no mirror or baseurl set.
Repository rawhide-debuginfo has no mirror or baseurl set.
Repository rawhide-source has no mirror or baseurl set.
Last metadata expiration check performed 0:10:56 ago on Fri Sep 4 19:54:17 2015.
Error: nothing provides libKF5Baloo.so.5()(64bit) needed by plasma-desktop-5.4.0-2.fc22.x86_64.
package sddm-breeze-5.4.0-6.fc22.1.noarch requires plasma-workspace = 5.4.0-6.fc22.1, but none of the providers can be installed.
package sssd-common-1.13.0-2.fc22.x86_64 requires libldb(x86-64) = 1.1.20, but none of the providers can be installed
(try to add '--allowerasing' to command line to replace conflicting packages)
The message about sssd-common though is very strange as they are both already installed:
libldb.x86_64 1.1.20-1.fc22 @System
sssd-common.x86_64 1.13.0-2.fc22 @System
Version-Release number of selected component (if applicable):
*** This bug has been marked as a duplicate of bug 1148627 ***
This is not an issue with the debug output of dnf, this is a packaging problem.
# dnf upgrade
Last metadata expiration check performed 22:08:46 ago on Thu Sep 10 13:14:58 2015.
Package Arch Version Repository Size
Skipping packages with broken dependencies:
libldb x86_64 1.1.21-1.fc22 updates 133 k
libldb-devel x86_64 1.1.21-1.fc22 updates 76 k
Nothing to do.
Having downloaded the packages...
# rpm -Uvh libldb-1.1.21-1.fc22.x86_64.rpm libldb-devel-1.1.21-1.fc22.x86_64.rpm
error: Failed dependencies:
libldb(x86-64) = 1.1.20 is needed by (installed) sssd-common-1.13.0-2.fc22.x86_64
It would seem that the current version of sssd-common is pinned to the 1.1.20 version of libldb, preventing its upgrade to 1.1.21
This is a packaging issue not an issue with debug output, so therefore is not a duplicate of bug 1148627