Hi Norbert, On Thu, Apr 14, 2005 at 08:25:17PM -0700, Norbert Kiesel wrote: > I get the following during upgrade > > Setting up slapd (2.2.23-2) ... > Backing up /etc/ldap/slapd.conf in /var/backups/slapd-2.2.23-1... > done. > Moving old database directories to /var/backups: > - directory dc=tbdnetworks,dc=com... done. > Loading from /var/backups/slapd-2.2.23-1: > - directory dc=tbdnetworks,dc=com... > /var/lib/dpkg/info/slapd.postinst: line 103: > /var/backups/slapd-2.2.23-1/dc=tbdnetworks,dc=com.ldif: No such file or > directory > /var/lib/dpkg/info/slapd.postinst: line 106: [: : integer expression > expected > failed.
Well, there is no need to load the database if upgrading a minor
version. Problem is that currently the postinst does not check wether it
has to import the database but just goes ahead and goes it. My fault!
> Looking into /var/backups, I see
> /var/backups/dc=tbdnetworks,dc=com-2.2.23-1.ldapdb/
> |-- DB_CONFIG
> |-- __db.001
> |-- __db.002
> |-- __db.003
> |-- __db.004
> |-- __db.005
> |-- dn2id.bdb
> |-- id2entry.bdb
> |-- log.0000000001
> `-- objectClass.bdb
Just moving that back to /var/lib/ldap or whereever your LDAP DB was
located should be fine. I'll fix this for the next release. Sorry for
the fuss!
> The upgrade from 2.1.30 to 2.2.23-1 failed in a similar way, but I
> thought I might have done something wrong so I did not report that.
If an upgrade fails the maintainer did something wrong - at least a
helpful message what the admin did wrong should be output. So - please
report such problems!
Greetings
Torsten
signature.asc
Description: Digital signature
