I think this proposed patch will not do anything to help people who've already upgraded from Lucid to Maverick, but who have just left the package half-configured because of this problem (since it won't trigger the upgrade if the $OLD_VERSION is "2.4.23-0ubuntu3", for example).
I guess that's unavoidable, since on a system in that situation the slapd.preinst wouldn't be able to run the database export, anyway (since the "slapcat" binary would also give the "Program version 4.8 don't match" error on such a system). Still, I wonder if it makes sense to have the changelog say something like "If you previously upgraded from a Lucid version of slapd to 2.4.23-0ubuntuX and haven't already manually upgraded the slapd database version, you will need to follow the steps described in that bug." or whatever? -- upgrade process does not upgrade underlying BDB format from 4.7 to 4.8 (so slapd aborts with "Program version 4.8 doesn't match environment version 4.7" error message) https://bugs.launchpad.net/bugs/658227 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
