Bug#325120: package: libpam-ldap unable to dlopen(/lib/security/pam_ldap.so
On Wed, Sep 14, 2005 at 05:56:48PM -0500, Chad Walstrom wrote: Ah, ha! It turns out that this bug is because libpam-ldap in sarge doesn't have appropriate versioned dependencies on libldap2. I had recompiled the openldap2 libraries and server on woody to enable SSL support way back when. Because I used an epoch in the version, it never got upgraded with the rest of the system to sarge. Still, because libpam-ldap doesn't have an appropriate versioned dependency, it didn't generate a conflict when it was installed. Doesn't that indicate that libpam-ldap *does* have an appropriate versioned dependency, which you violated by versioning your local package with an epoch that's not present in the Debian archive? The shlibs system of shared library handling in Debian depends on monotonically increasing version numbers for packages; representing your library as a newer version of an existing Debian package, when it lacks symbols that have been added in later upstream versions, breaks this constraint, but that doesn't make the package's dependencies incorrect. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Bug#325120: package: libpam-ldap unable to dlopen(/lib/security/pam_ldap.so
Steve Langasek [EMAIL PROTECTED] wrote: Doesn't that indicate that libpam-ldap *does* have an appropriate versioned dependency, which you violated by versioning your local package with an epoch that's not present in the Debian archive? Probably. The shlibs system of shared library handling in Debian depends on monotonically increasing version numbers for packages; representing your library as a newer version of an existing Debian package, when it lacks symbols that have been added in later upstream versions, breaks this constraint, but that doesn't make the package's dependencies incorrect. Make sure the same isn't true for the original submitter. The problem is definitely a library conflict between libldap2 of the era 2.0.23 v.s. the newer libpam-ldap. -- Chad C. Walstrom [EMAIL PROTECTED]247 Gortner Hall http://www.umn.edu/~ccw Help: 612-625-9284 http://cbs.umn.edu/main/ComputingServices Phone: 612-624-2918 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#325120: package: libpam-ldap unable to dlopen(/lib/security/pam_ldap.so
Ah, ha! It turns out that this bug is because libpam-ldap in sarge doesn't have appropriate versioned dependencies on libldap2. I had recompiled the openldap2 libraries and server on woody to enable SSL support way back when. Because I used an epoch in the version, it never got upgraded with the rest of the system to sarge. Still, because libpam-ldap doesn't have an appropriate versioned dependency, it didn't generate a conflict when it was installed. Why the older version in sarge worked with openldap2 v2.0.23 libraries, I do not know. It may have something to do with activation of threading and reliance on the reentrant versions of the ldap library. -- Chad C. Walstrom [EMAIL PROTECTED]247 Gortner Hall http://www.umn.edu/~ccw Help: 612-625-9284 http://cbs.umn.edu/main/ComputingServices Phone: 612-624-2918 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#325120: package: libpam-ldap unable to dlopen(/lib/security/pam_ldap.so)
Package: libpam-ldap Version: 178-1sarge1 arch:i386 After having installed the security related package libpam-ldap 178-1sarge1 I receive the following error messages (on a file server running samba): Aug 26 10:22:35 emlsv22 smbd[3566]: PAM adding faulty module: /lib/security/pam_ldap.so Aug 26 10:22:37 emlsv22 smbd[3712]: PAM unable to dlopen(/lib/security/pam_ldap.so) Aug 26 10:22:37 emlsv22 smbd[3712]: PAM [dlerror: /usr/lib/libldap_r.so.2: undefined symbol: pthread_create] Aug 26 10:22:37 emlsv22 smbd[3712]: PAM adding faulty module: /lib/security/pam_ldap.so Aug 26 10:22:37 emlsv22 smbd[3712]: [2005/08/26 10:22:37, 0] auth/pampass.c:smb_pam_account(573) Aug 26 10:22:37 emlsv22 smbd[3712]: smb_pam_account: PAM: UNKNOWN PAM ERROR (9) during Account Management for User: vogeljn Aug 26 10:22:37 emlsv22 smbd[3712]: [2005/08/26 10:22:37, 0] auth/pampass.c:smb_pam_accountcheck(781) Aug 26 10:22:37 emlsv22 smbd[3712]: smb_pam_accountcheck: PAM: Account Validation Failed - Rejecting User username! - Kernel Version: Linux emlsv22 2.6.10 #1 Fri Feb 11 12:44:39 CET 2005 i686 GNU/Linux, libc6 2.3.2.ds1-22 Regards, A. Beck -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
