I was in the middle of testing this, too, when Randy posted his message. I got the same results he did for the 0.8.4 -> 0.8.4ubuntu0.3 and 0.8.4 -> 0.8.4ubuntu0.4 upgrades, using the "uri" value to test the upgrade behavior.
Also, to follow up on the original report in Bug #1350778, I did an additional test regarding the tls_reqcert value. I changed that setting using "dpkg-reconfigure nslcd" (thus producing a non-working nslcd configuration), changed the line back using "vi nslcd.conf" to get a working config, and then ran "dpkg-reconfigure -u nslcd" to see which of the two settings took precedence. When I did this test with 0.8.4ubuntu0.4, the nslcd.conf file was not changed, but instead the debconf database value was overwritten with the value taken from the nslcd.conf file, as desired. So it looks like this patch does resolve the specific failure scenarios mentioned in both of these bugs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229713 Title: nslcd auto-configuration disregards existing nslcd.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss-pam-ldapd/+bug/1229713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
