> Il giorno lun, 26/02/2007 alle 12.38 -0800, Steve Langasek ha scritto: > [...] > > The nature of this bug is that the libpam-ldap.conf has > been manually > > edited, and on upgrade the user is *not* prompted again, > but the local > > changes are overwritten instead. That's the behavior that > needs to be > > addressed here. > [...] > > I will work again on this package tomorrow and I hope to > have the fix ready for both packages libpam-ldap and libnss-ldap. > I have one question: you changed the configuration file by > hand, but did you remove the first line containing "###DEBCONF###" ?
No I haven't done that. It's not clear what settings debconf manages in the .conf file, as there are many that pertain to an ldap setup and only a few questions are posed by debconf to setup the initial conf file. It's also not clear that it manages the .secret file, which simply contains the password for the rootbinddn. My systems do not use the "host" setting, but the "uri" instead to specify ldaps://. I may change the rootbinddn, and password in the .secret file at a later date. That is the situation that the package needs to deal with, because my setup should not be quietly broken by a debian upgrade, but currently it does break it. IMHO software is normally re-configured using the configuration files, and debconf mostly plays it's roll in the initial install. If I did dpkg-reconfigure, I understand it would re-write the settings I specify at that point. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
