Hi Thomas, On Wed, Apr 13, 2005 at 04:37:04PM +0200, Thomas Prokosch wrote: > During the upgrade from slapd version 2.1 to 2.2 I noticed that the > configuration file /etc/ldap/slapd.conf is altered. It is a nice feature to > have the configuration altered to match a new slapd version (kudos to the > implementor), it works really well.
It's still mostly a proof of concept. I wanted to test if implementing
this feature is feasible before adding all the boiler plate. The upload
to unstable was a bit premature but I thought that people running
unstable will be able to deal with the problems of the current package.
The missing backup feature was an oversight (everything else is backed
up by default) and is already listed in debian/TODO of the source
repository, targetted for 2.2.23-2:
* debian/slapd.postinst: Make a backup copy of slapd.conf before
changing anything (closes: #304485).
I hope to get this fixed the next days.
> The Debian policy states that maintainer scripts must "not overwrite or
> otherwise mangle the user's configuration without asking", so I think making
> a backup copy would be a good idea.
Yes, I was thinking about a debconf template for this. I am not sure
though if I want to ask a separate question for each issue.
Greetings
Torsten
signature.asc
Description: Digital signature
