| > Right now I'm in the chicken and egg situation where I cannot re/install | > new slapd cleanly, because it always dies with this error. | | It will fail in a different place then. The whole problem is that the | maintainer scripts always try to load the database contents in 2.3.23-2 | wether the database was dumped or not. | | Work around in your case: | | - back up the configuration | - purge the slapd package | - reinstall the package and omit the configuration | - copy the database files and configuration back in place | (db files from /var/backups/<basedn>-2.3.23-1.ldapdb to /var/lib/ldap)
I managed to make the upgrade happen, but I think this si not satisfactory. I think the package should recover from a case like: apt-get --purge remove x apt-get install x I think, at minimum there should be better error handling and a message displayed to a user what might be the reason for the failure and how to fix it. After looking at the code, the error handling is lacking now. Could that be improved? I'm not still sure what is the real problem with the upgrade, so the cause may be deeper. Jari -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
