On 12-03-11 at 11:12am, Moritz Muehlenhoff wrote: > as part of the hardening release goal I tried to recompile libnss-ldap > with current cdbs: > > Here's how the sonames are with the version currently in the archive: > > jmm@pisco:~/scratch/libnss-ldap-264$ dpkg -L libnss-ldap | grep ^/lib > /lib > /lib/libnss_ldap-2.11.2.so > /lib/libnss_ldap.so.2 > > Here's how they look like after a rebuild with current cdbs: > > jmm@pisco:~/scratch$ dpkg -L libnss-ldap | grep ^/lib > /lib > /lib/libnss_ldap-.so > /lib/libnss_ldap.so. > > I don't know anything about the internals of cdbs, but this looks like > a bug in cdbs, rather than in libnss-ldap's use of cdbs?
Generally I would appreciate if you verified by building against an older release of CDBS. This package depends unversioned on CDBS so should (in my interpretation - it is not officially defined TTBOMK) support _any_ officially released CDBS i.e. even the one in oldstable (until that one is no longer officially supported by Debian). Specifically, I did a brief(!) look at the source package, saw no obvious risk that CDBS caused this problem, but noticed that a) last maintainer upload was in 2009, b) I believe the package is generally discouraged and practically replaced by libnss-ldapd, and c) topmost Makefile.am in upstream code seemingly resolve version using "gcc -print-multi-os-directory" against _other_ libraries, a mechanism that looks suspocious to me and that I guess is affected by recent multiarch changes. Perhaps package is unmaintained and should die? - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: Digital signature
