Bug 705338

Summary: nss_ldap dependency failure
Product: [Fedora] Fedora Reporter: John Crowley <j.crowley>
Component: glibcAssignee: Andreas Schwab <schwab>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: dpal, fweimer, jakub, nalin, schwab
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-17 13:01:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description John Crowley 2011-05-17 12:19:50 UTC
Description of problem: nss_ldap will not install via yum -- dependency failure


Version-Release number of selected component (if applicable):


How reproducible: Yes


Steps to Reproduce:
1. yum install nss_ldap
2.
3.
  
Actual results:
--> Running transaction check
---> Package nss_ldap.i686 0:265-8.fc15 will be installed
--> Processing Dependency: nscd for package: nss_ldap-265-8.fc15.i686
--> Running transaction check
---> Package nscd.i686 0:2.13.90-9 will be installed
--> Processing Dependency: glibc = 2.13.90-9 for package: nscd-2.13.90-9.i686
--> Finished Dependency Resolution
Error: Package: nscd-2.13.90-9.i686 (fedora)
           Requires: glibc = 2.13.90-9
           Installed: glibc-2.13.90-11.i686 (@updates-testing)
               glibc = 2.13.90-11
           Available: glibc-2.13.90-9.i686 (fedora)
               glibc = 2.13.90-9
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest


Expected results: successful installation


Additional info: Believe that this also causes LDAP to not be used as expected for login

Comment 1 Dmitri Pal 2011-05-17 12:53:35 UTC
This is an nscd issue not nss_ldap.

Comment 2 Andreas Schwab 2011-05-17 13:01:30 UTC
yum distro-sync

Comment 3 John Crowley 2011-05-17 13:32:03 UTC
Nuts!  Did yum distro-sync and now yum itself is broken -- it looks like I'm back to a re-install.  Maybe will just wait for final release.

============================================================
yum list all
There was a problem importing one of the Python modules
required to run yum. The error leading to this problem was:

   libgcc_s.so.1: cannot open shared object file: No such file or directory

Please install a package which provides this module, or
verify that the module is installed correctly.

It's possible that the above module doesn't match the
current version of Python, which is:
2.7.1 (r271:86832, Apr 12 2011, 16:16:18)
[GCC 4.6.0 20110331 (Red Hat 4.6.0-2)]

If you cannot solve this problem yourself, please go to
the yum faq at:
  http://yum.baseurl.org/wiki/Faq