Bug 604978
Summary: | file /usr/lib64/libnss_ldap.so conflicts between attempted installs of nss-pam-ldapd-0.7.6-2.fc14.x86_64 and nss_ldap-265-4.fc14.x86_64. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jens Petersen <petersen> |
Component: | nss-pam-ldapd | Assignee: | Nalin Dahyabhai <nalin> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | nalin |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-06-24 21:01:34 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jens Petersen
2010-06-17 07:53:43 UTC
(In reply to comment #0) > Description of problem: > file /usr/lib64/libnss_ldap.so conflicts between attempted installs of > nss-pam-ldapd-0.7.6-2.fc14.x86_64 and nss_ldap-265-4.fc14.x86_64. Yeah, you really only want one or the other installed at any given time. When libc goes to load libnss_ldap.so.2 to look up information, it's just going to use the first one it finds (unless $LD_LIBRARY_PATH is in use, and I wouldn't recommend it generally here). > Steps to Reproduce: > - yum install nss-pam-lapd on rawhide. > > or > > - try to install rawhide > > Is it intentional that is it installed by default in f14? > > from @base: > <packagereq type="default">nss-pam-ldapd</packagereq> The change of which of the two is installed by default is intentional, yes. I can't put an "obsoletes:" in there because I'm trying to not surprise people on upgrades. That said, if you have an idea for avoiding problems here, I'm open. So notabug? I guess not, though I continue to be open to ideas here. Thanks! Hmm, so no way to install rawhide until Alpha? Um, what? Can you elaborate on what's going on here? Sorry for being unclear.
> (In reply to comment #0)
> > - try to install rawhide
I can't install rawhide because of this conflict.
That's not more information than I had before. How are you installing? Are you upgrading using yum? Are you installing from a nightly live CD? Are you booting from F13 media and then adding a Raw Hide repository? If you're booting from F13 media, are you leaving the F13 repositories enabled? Either way, do you know if both packages are being selected from the start, or is one selected, with the second being pulled in because of dependencies? If you're using anaconda one way or another, and both are somehow being selected by default, what happens when you customize package selection and turn one of them off? (In reply to comment #7) > How are you installing? Are you upgrading using yum? Are you installing from > a nightly live CD? Are you booting from F13 media and then adding a Raw Hide > repository? If you're booting from F13 media, are you leaving the F13 > repositories enabled? (Nightly live does not boot for me.) Yes, it is a net install via f13 and switching to rawhide repo: ie replacing the f13 repo with rawhide. > Either way, do you know if both packages are being selected from the start, or > is one selected, with the second being pulled in because of dependencies? If > you're using anaconda one way or another, and both are somehow being selected > by default, what happens when you customize package selection and turn one of > them off? Dunno if it could be some anaconda weirdness with the switching of repo. I will try now to deselect nss-pam-ldapd. So yes if I customize and unselect:
> <packagereq type="default">nss-pam-ldapd</packagereq>
The conflict does not occur in anaconda.
So do you want to remove it from @base or make it optional? :)
If you like I can also commit the change to comps.git. Is anaconda somehow attempting to merge the definitions of the package group across all of the repositories, even the disabled ones? I could live with the package being optional -- it's only default because it's replacing nss_ldap as a default package in the group. But then sssd is already in there as a default, and authconfig will prefer it over nss-pam-ldapd, so yeah, might as well make both it and pam_ldap optional. I'll get to that later today if you don't get there first. Thanks! Done, moving to closed. Please reopen if this continues to create problems with the next Raw Hide push. |