On Thu, Oct 14, 2010 at 17:47:19 -0000, Steve Langasek wrote: > Ah, you're probably right then and I'm just > misremembering how this was > handled in Debian.
Looking through the Debian changelog, it appears that there was a similar problem between 2.4.23-1 and 2.4.23-4. The switch to libdb4.8 was made in 2.4.23-1, but the change to slapd.scripts-common made at that time (SVN revision 1275) used "lt-nl 2.4.21" as the conversion cutoff, so the export/import cycle was missed for systems upgrading from 2.4.21-1. This was corrected in 2.4.23-4 (SVN 1307) after being reported in debbugs #593550. I see that the correction does use "2.4.23-4" as the cutoff version number, so I think that in Debian there would be errors attempting to upgrade from a pre-2.4.23 database to one of the earlier 2.4.23 packages (but without doing any manual fixes) and then up to the -4 version. But it also looks like 2.4.23-4 was the first of the 2.4.23 versions to make it into Testing, so presumably there weren't too many people affected by that gap. In Ubuntu we have the situation that the "gap" includes the version released in Maverick, so it seems likely to affect more people.... 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