Processing control commands:
severity -1 important
Bug #696445 [nslcd] nslcd: Discards local modifications in nslcd.conf without
warning
Severity set to 'important' from 'serious'
tags -1 + unreproducible
Bug #696445 [nslcd] nslcd: Discards local modifications in nslcd.conf without
warning
Control: severity -1 important
Control: tags -1 + unreproducible
On Fri, 2013-03-01 at 16:02 -0800, Russ Allbery wrote:
Should this bug be downgraded until it can be confirmed as
reproducible? I also looked through the postinst script and, while
it's complex, I didn't see any obvious way in
Should this bug be downgraded until it can be confirmed as reproducible?
I also looked through the postinst script and, while it's complex, I
didn't see any obvious way in which it could produce the behavior
described here.
--
Russ Allbery (r...@debian.org)
Hi Arno,
On Sun, 2012-12-23 at 12:39 +0100, Arthur de Jong wrote:
Do you by any change have the configuration file before and after the
upgrade?
Also, can you confirm that this debconf information was in place after
the upgrade for the broken machine:
* nslcd/ldap-auth-type: none
*
On Thu, 2012-12-20 at 22:24 +0100, Arno wrote:
Which was caused by the removal of the line
tls_cacertfile /etc/ssl/certs/loos.site.pem
from nslcd.conf on upgrade.
This is really weird, nslcd package scripts shouldn't do anything with
this option (neither this version or any before).
Do
On Fri, 2012-12-21 at 12:40 +0100, Dominik George wrote:
I have looked into the config and postinst script to find some hints on
why this might happen. Here are some remarks, be they relevant or not:
Thanks for the feedback. Always good to have another set of eyes looking
at the code.
- Using
Package: nslcd
Followup-For: Bug #696445
Control: tags -1 + moreinfo
Hi,
I have looked into the config and postinst script to find some hints on
why this might happen. Here are some remarks, be they relevant or not:
- Using backticks in shell scripts is incompatible and might break with
some
Package: nslcd
Version: 0.8.10-4
Severity: serious
Justification: changes to configuration files must be preserved during a
package upgrade
It seems that a combination of #661872, #671464, and/or #689296 is back again
with version 0.8.10-4.
After upgrading nslcd today, my system stopped
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
9 matches
Mail list logo
