severity 595464 minor thanks On Sat, Sep 04, 2010 at 09:04:04AM +0200, Vincent Danjean wrote: > The only working tip has been to manually edit /var/cache/debconf/config.dat > and set slapd/move_old_database to true. > And then: > r...@ogmios:/home/vdanjean# dpkg -a --configure > Paramétrage de slapd (2.4.23-4) ... > Backing up /etc/ldap/slapd.conf in /var/backups/slapd-2.4.17-2.1... done. > Moving old database directories to /var/backups: > - directory dc=danjean,dc=fr... done. > Loading from /var/backups/slapd-2.4.17-2.1: > - directory dc=danjean,dc=fr... done. > - chowning database directory (openldap:openldap)... done > Migrating slapd.conf to slapd.d configuration style... done. > Starting OpenLDAP: slapd.
> You should really propose easiest way to upgrade slapd when non standard > configuration is found (at least, a way to leave the package in a installed > state even if the config migration is not completed). > Perhaps, reasking the slapd/move_old_database question can be a solution (at > least for interactive upgrade) This has nothing to do with non-standard configurations, and everything to do with the fact that you had set slapd/move_old_database to 'false' in debconf. Why did you do this? This is a low-priority debconf question that defaults to 'true'. It is possible to handle this migration by hand if you choose (not a good idea IMHO, but possible). You just need to leave the directory in place, so slapadd has somewhere to write since it won't create the path for you. Marking the package as "installed" when the maintainer scripts have failed to upgrade the directory to a DB version that will actually run with the current slapd would be an error. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected]
signature.asc
Description: Digital signature
