On Thu, Oct 14, 2010 at 16:31:20 -0000, Steve Langasek wrote:
> That's not unavoidable; just bump the minimum version check to the
> maverick release version instead of the lucid version. New
> installations of maverick will get an excess database dump/restore, but
> the upgrade will be clean for everyone.
Yeah, that's what I was going to suggest at first, but I don't think it
will cover all the cases.
Say someone had a working Lucid version of slapd they've already tried
upgrading to the Maverick release 2.4.23-0ubuntu3, and they haven't ever
done the manual "db4.7_XXXX" steps to convert the database. In that
case, they'll still have a v4.7 BDB environment in their /var/lib/ldap
directory... but the version of slapcat installed on their machine will
be from 2.4.23-0ubuntu3.
That is, they'll already have a slapcat linked against libdb4.8, and so
the slapd.pre/postinst scripts won't be able to export the "old"
database in preparation for importing it using the "new" version.
I don't have an environment available where I can actually test this
myself, but as far as I can see once someone has installed slapd
2.4.23-0ubuntu3 it's too late to try fixing this problem with the usual
export/import cycle....
Nathan
--
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
Server Team, which is subscribed to openldap in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
