Comment 14 for bug 450645

For what it's worth, I just had this error when trying to upgrade to to the recent Lucid slapd upgrade:

==============================================================
Preparing to replace slapd 2.4.21-0ubuntu5 (using .../slapd_2.4.21-0ubuntu5.3_amd64.deb) ...
Stopping OpenLDAP: slapd.
Unpacking replacement slapd ...
[...]
Setting up slapd (2.4.21-0ubuntu5.3) ...
  Backing up /etc/ldap/slapd.d/ in /var/backups/slapd-2.4.21-0ubuntu5... done.
chown: cannot access `olcDbDirectory\nolcDbDirectory': No such file or directory
dpkg: error processing slapd (--configure):
 subprocess installed post-installation script returned error exit status 1
[...]
Errors were encountered while processing:
 slapd
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up slapd (2.4.21-0ubuntu5.3) ...
  Backing up /etc/ldap/slapd.d/ in /var/backups/slapd-2.4.21-0ubuntu5... done.
chown: cannot access `olcDbDirectory\nolcDbDirectory': No such file or directory
dpkg: error processing slapd (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 slapd
Press return to continue.
==============================================================

In my case the trigger for this error was the "olcDatabase={1}hdb.ldif~" file that I had created manually a few months ago as part of my testing before posting my earlier comments on this bug.

Still, I was able to get the upgrade to complete successfully by tweaking the postinst script to limit the "grep" calls to files whose names actually end in ".ldif", and I wonder if there is any reason not to apply that patch (or something similar) to the package?