Comment 6 for bug 1229713

This behavior was fixed on bzr branch in the following revision:

----
revno: 19 [merge]
tags: 0.8.8-1
fixes bugs: http://bugs.debian.org/670419 http://bugs.debian.org/669680 http://bugs.debian.org/670133
author: Arthur de Jong <email address hidden>
committer: Package Import Robot <email address hidden>
branch nick: sid
timestamp: Fri 2012-04-27 13:20:00 +0200
message:
  * new upstream release:
    - fix a problem in the handling of PAM requests in nslcd (closes: #670419)
    - install the ldapns.schema in nslcd docs (closes: #669680)
  * use the configuration file contents to determine the authentication
    type, not the debconf database (closes: #670133)
  * switch PAM account type to primary because it now does all the
    authorisation checks that pam_unix also does
  * drop functionality to check whether shadow information is exposed
    in /etc/nsswitch.conf, it was no longer needed sine 0.8.4
  * ensure that /var/run/nslcd is not removed during upgrades
----

So this fix is already present in Trusty & Utopic.

----
Since this fix is straight-forward I have cherry-picked:

  * [bzr lp:ubuntu/nss-pam-ldapd revno:19 tag:0.8.8-1]:
    - debian/nslcd.config: properly handle preseeding and reading values
    from the configuration file by forcefully overwriting debconf values
    from nslcd.conf and not overwriting debconf values when reading other
    configuration files. (LP: #1229713)

Changing the following files:

- debian/nslcd.config
- debian/changelog (of course)

----

I have also created one PPA so this fix can be tested by users:

# add-apt-repository ppa:inaddy/lp1229713
# apt-get update
# apt-get install nss-pam-ldapd

This will install version 0.8.4ubuntu0.4~lp1229713~2 which will be superseded by 0.8.4ubuntu0.4 when and if a SRU is available.

Appreciate if whoever suffers from this issue, and is willing to test, could give me feedback on this. The change only ignores already set debconf values unless "force" parameter (for parsecfg function) is given.

Thank you.