Package: nslcd Version: 0.8.10-4 Followup-For: Bug #696445 I must add that this does not happen on all machines, on this second machine the upgrade did not clobber the configuration file. The only difference I can think of as relevant is that the earlier machine has been running testing since its creation 6 months ago, and the other was only recently upgraded from Squeeze.
Clobbered (murid): 0.8.9-1 0.8.10-1 0.8.10-2 0.8.10-4 xx Not clobbered (gnome): 0.7.15 0.7.15+squeeze1 0.7.15+squeeze2 0.8.10-2 0.8.10-4 I'm happy to provide more information, but I don't know what would help you. Regards, Arno -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (900, 'stable'), (300, 'unstable'), (200, 'stable-updates') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages nslcd depends on: ii adduser 3.113+nmu3 ii debconf [debconf-2.0] 1.5.46 ii libc6 2.13-37 ii libgssapi-krb5-2 1.10.1+dfsg-3 ii libldap-2.4-2 2.4.31-1 Versions of packages nslcd recommends: ii bind9-host [host] 1:9.8.1.dfsg.P1-4.4 ii ldap-utils 2.4.31-1 ii libnss-ldapd [libnss-ldap] 0.8.10-4 ii libpam-krb5 4.6-1 ii libpam-ldapd [libpam-ldap] 0.8.10-4 ii unscd [nscd] 0.48-2 Versions of packages nslcd suggests: pn kstart <none> -- debconf information: nslcd/ldap-sasl-realm: * nslcd/ldap-starttls: true * nslcd/ldap-reqcert: demand nslcd/ldap-sasl-secprops: * nslcd/ldap-binddn: * nslcd/ldap-base: dc=loos,dc=site nslcd/ldap-sasl-krb5-ccname: /var/run/nslcd/nslcd.tkt * nslcd/ldap-auth-type: none * nslcd/ldap-uris: ldapi:///var/run/slapd/ldapi ldap://genie.loos.site/ ldap://gnome.loos.site/ nslcd/ldap-sasl-authcid: nslcd/ldap-sasl-mech: nslcd/ldap-sasl-authzid: -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
