[Pkg-openldap-devel] Bug#546368: Post-installation script for slapd fails to update to new db version

[Dmitry Katsubo]

Hi Steve,

Thanks for your comments.

On 13.09.2010 9:21, Steve Langasek wrote:
> Why does it produce these dummy entries?  It sounds to me like you took the
> default database created at package install and changed the database suffix
> without first removing the files belonging to the existing database.

Yes, you are probably right: I haven't truncated the default database
before filling in the new data. After the update I had to recover LDAP
database from backup LDIFF, which didn't contain the "erroneous" data
referring "dc=nodomain". My fault. But I couldn't avoid this trap, as I
didn't know the databases contains some extra entries describing some
other domain. So what I can suggest (and maybe you come with better
solution) is:

- Installation does not add any entries to slapd database by default,
leaving it empty. Maybe document something in README.Debian... hopefully
someone reads it.
or
- Update script checks the data for consistency after/during a dump. It
should fail the package update, asking the administrator to fix the
database before doing the actual update. Otherwise update will fail at
later stage, leaving the database empty which is a catastrophe.

-- 
With best regards,
Dmitry