|
| Hrm, too bad, what went wrong during the upgrade?
Don't know. I haven't touched anything in between the previous install
and this one.
| > (Reading database ... 120482 files and directories currently installed.)
| > Unpacking slapd (from .../slapd_2.2.23-2_i386.deb) ...
| > Setting up slapd (2.2.23-2) ...
| > Backing up /etc/ldap/slapd.conf in /var/backups/slapd-2.2.23-1... done.
| > Enabling LDAPv2 support... already enabled.
| > Moving old database directories to /var/backups:
| > Loading from /var/backups/slapd-2.2.23-1:=20
|
| =2E.. makes no sense. Bug in maintainer scripts, it assumes the files are
| there.=20
|
| > The offending code:
| >=20
| > 96 automatic_ldif_fixing_wanted_for() {
|
| That function is right. It has to be called with an ldif file as
| paremeter. Which must be there obviously :) The codepath to that
| function should never get invoked though.
Right now I'm in the chicken and egg situation where I cannot install
new slapd cleanly, because it always dies with this error. Could you
add this further checks to this function in order to ignore the file
if it does not exist. Possibly suggestion to user that
dpkg-reconfigure may be needed to recreate files.
Jari
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
