Hello Torsten, Torsten Landschoff torsten-at-debian.org |bugs-debian| wrote: > 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.
Just perfect timing, when one knows debconf-communicate ;-) > 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. Great. Feel free to close this bug ;-) I just think reporting earlier is better than experiencing data loss or similar things. > On Wed, Apr 13, 2005 at 04:37:04PM +0200, Thomas Prokosch wrote: >>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. It came to my mind that the question which sets slapd/dump_database already implies whether a backup copy is desired. In case of "always" and "when needed" a backup copy should be made, in the other case do not touch the configuration and do not create a backup. Another question would be redundant IMHO. Have a nice evening, Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
