slapd fails to upgrade if included schema files are no longer available - evolution.schema not available anymore

[Phil Lello]

Crash during end of Hardy upgrade. Previous errors had been reported with the slapd-2.4.7-6ubuntu4.2_i386.deb package (pre-installation script returned error status 1, then later package is already installed and configured)

ProblemType: Package
Architecture: i386
Date: Thu Jun 12 23:12:29 2008
DistroRelease: Ubuntu 8.04
ErrorMessage:
 ErrorMessage: package slapd is already installed and configured
Package: slapd 2.3.35-1ubuntu0.2
PackageArchitecture: i386
SourcePackage: openldap2.3
Title: package slapd 2.3.35-1ubuntu0.2 failed to install/upgrade:
Uname: Linux 2.6.22-14-generic i686

[Phil Lello (phil-lello)]

I managed to get the package to install correctly after changing my /etc/ldap/slapd.conf, to update the include for evolutionperson.schema to /usr/share/evolution-data-server-2.22/evolutionperson.schema.

This had been left pointing at the pre-hardy path of /usr/share/evolution-data-server-2.22/evolutionperson.schema

As a minimum, I'd recommend that missing schemas shouldn't cause the slapd upgrade to fail, although I don't know what action should be taken (if any) to correct this. In this case, I guess includes from different packages should be checked for before anything gets uninstalled, but I have no idea how complex this might be to do.

Phil

[Mathias Gug (mathiaz)]

I think that missing schema files should lead to a failed upgrade.

If we'd allow the upgrade to succeed, the resulting configuration would be wrong and slapd won't start anyway. Commenting out the missing schema is not a good option as it would break the client applications (and slapd won't probably start as it doesn't know about some parts of the ldap objects stored in the database).

However this use case should be be improved when we're migrating to the cn=config backend.