I am not seeing this behavior with version 0.4 (uploaded today). Please
re-open if you continue to see this bug.
** Changed in: ldap-auth-client (Ubuntu)
Status: In Progress => Fix Released
--
/etc/ldap.conf removed
https://bugs.launchpad.net/bugs/134354
You received this bug notificatio
Yes, I had libpam-ldap and libnss-ldap previously installed and working.
I then manually installed ldap-auth-client (I can't remember if libpam-ldap
and libnss-ldap got upgraded at the same time), answering NO to the local
root question.
BTW it is easily retriggerable by dpkg-reconfiguring ldap-au
Actually, I think I misunderstood the bug. Had you installed a previous
libpam_ldap package and ldap-auth-client was installed as a prereq
during an upgrade? If so, ldap.conf should not preexist. I'm pretty
sure this must be a use case I missed, I just need to narrow down
exactly what you are do
This fix will be uploaded shortly.
** Changed in: ldap-auth-client (Ubuntu)
Importance: Undecided => High
Assignee: (unassigned) => Rick Clark
Status: New => In Progress
--
/etc/ldap.conf removed
https://bugs.launchpad.net/bugs/134354
You received this bug notification because you
