On Thu, Oct 14, 2010 at 05:32:03PM -0000, Nathan Stratton Treadway wrote: > 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. Ah, you're probably right then and I'm just misremembering how this was handled in Debian. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected] -- 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
