Comment 12 for bug 364531

I've been able to eventually migrate to Jaunty slapd. As I was expecting, it was not configuration related because slaptest -u would told me that my config fil was fine. Here are the step I followed :

1) Stop slapd. Backup and remove /etc/ldap and /var/lib/ldap. With them, upgrade is impossible for reasons I don't understand.

2) upgrade packages with apt

3) stop slapd.

4) restore /etc/ldap and /var/lib/ldap

5) remove /var/lib/ldap/log.000000001 (no need to backup it)

6) cd /var/lib/ldap then run db4.6_restore -h . -v

At this point, it will tell you that 4.7 is the environement version.

7) Run once again db4.6_restore -h . -v You have to run it at least twice, else it doesn't work.

8) chown openldap:openldap log.000000001

9) Start ldap, your migration is now over.

The bugs are the following :

A) The install script of the slapd package seems completely crazy when dealing with an existing installation. It backup everything in strange ways and fails miserably if not everything is like expected. It should be more defensive.

B) slapd should be able to restore by itself a database when the log file is missing. It was the case with the slapd in intrepid, I've no idea why it's not working anymore in jaunty