I'm not sure that this bug applies to ldapscripts - it is caught out by the lack of a dependency:
> Setting up libnss-ldap (261-2) ... > invoke-rc.d: unknown initscript, /etc/init.d/nscd not found. > dpkg: error processing libnss-ldap (--configure): > subprocess post-installation script returned error exit status 100 > dpkg: dependency problems prevent configuration of ldapscripts: > ldapscripts depends on libnss-ldap; however: > Package libnss-ldap is not configured yet. > dpkg: error processing ldapscripts (--configure): > dependency problems - leaving unconfigured It is libdnss-ldap that fails, not ldapscripts - maybe this is actually a bug in libdnss-ldap in that it *Recommends* nscd, not Depends: Depends: libc6 (>= 2.7-1), libcomerr2 (>= 1.33-3), libkrb53 (>= 1.6.dfsg.2), libldap-2.4-2 (>= 2.4.7), libsasl2-2, debconf | debconf-2.0 Recommends: nscd, libpam-ldap nscd is the package containing /etc/init.d/nscd - I don't see how that can be a Recommends: unless libnss-ldap wraps the call to invoke-rc.d in a check for /etc/init.d/nscd Either way, isn't this a bug in libnss-ldap, not ldapscripts? It just shows up in ldapscripts. -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
pgpCMckUdynaH.pgp
Description: PGP signature
