Comment 2 for bug 536958

I did some more investigation into this issue, and it looks like this bug will affect all Hardy -> Lucid upgrades.

To test this I went through the following steps:

On a machine running Hardy (and which had never had "slapd" installed before):
1a) installed the "slapd" package, allowed the postinst script to configure the installation in the normal manner, and then ran "/etc/init.d/slapd stop" to cleanly shut down the daemon process.

1b) ran "slaptest -f /etc/ldap/slapd.conf" and confirmed that the BDB v4.2 database files did not cause any errors on that machine.

Back on the server recently upgraded to Lucid, I made a simple test directory:
2a) Created a test directory "/root/ldap_hardy_test", and under that an empty subdirectory "libldap".

2b) copied /etc/ldap/slapd.conf.old to ldap_hardy_test/slapd.conf, and edited the "directory" line to point to the /root/ldap_hardy_test/libldap directory.

2c) copied all files in /var/lib/ldap/ into /root/ldap_hardy_test/libldap/

2d) ran "slaptest -f slapd.conf -d 1" to confirm that the slaptest run completed without errors, and that it opened the files in ldap_hardy_test/libldap instead of /var/lib/ldap .

Then I tested the BDB files from the Hardy install:
3a) deleted all files in /root/ldap_hardy_test/libldap, and then copied all the files from the Hardy machine's /var/lib/ldap/ directory into the Lucid machine's "libldap" directory.

3b) ran "slaptest -f slapd.conf" again... and got the " Program version 4.7 doesn't match environment version" error message.

So, it appears that the BDB database files from even the simplest Hardy slapd install with trigger this error....