Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#38893 - [nss-pam-ldap][pam_ldap] file conflict
Attached to Project:
Community Packages
Opened by RbN (RbN) - Thursday, 13 February 2014, 14:33 GMT
Last edited by Jelle van der Waa (jelly) - Monday, 09 June 2014, 19:02 GMT
Opened by RbN (RbN) - Thursday, 13 February 2014, 14:33 GMT
Last edited by Jelle van der Waa (jelly) - Monday, 09 June 2014, 19:02 GMT
|
DetailsDescription:
/usr/lib/security/pam_ldap.so exists in both 'pam_ldap' and 'nss-pam-ldapd' Steps to reproduce: pacman -S pam_ldap nss-pam-ldap |
This task depends upon
Closed by Jelle van der Waa (jelly)
Monday, 09 June 2014, 19:02 GMT
Reason for closing: Fixed
Additional comments about closing: Removed pam_ldap from replaces and added it to conflics=()
Monday, 09 June 2014, 19:02 GMT
Reason for closing: Fixed
Additional comments about closing: Removed pam_ldap from replaces and added it to conflics=()
Comment by Doug Newgard (Scimmia) -
Friday, 30 May 2014, 17:09 GMT
- Field changed: Severity (Medium → High)
nss-pam-ldap actually has pam_ldap in replaces. This can't be right, since pam_lsap still exists. This also makes pam_ldap a real pain, since pacman will want to replace it every time you update. Same thing with nss_ldap. Something really needs done here.