On Thu, Oct 14, 2010 at 19:07:47 -0000, Mathias Gug wrote: > + if dpkg --compare-versions "$OLD_VERSION" lt-nl 2.4.23-0ubuntu3.1; then > return 0 > else > > > That will force a database dump for every upgrade to > maverick. This is the same fix as in Debian (modulo the > package revision). > > It won't address the use case outlined in comment 17. > For users that have already upgraded to maverick the > workaround outlined in the bug description should be > followed.
Again, I don't have a way to actually test this, but I believe that putting the "0ubuntu3.1" onto the comparison means that in the case described in comment 17, the upgrade script will attempt to do the export/import but will not be able to do so (because the existing slapcat will not be compatible with the existing db files), and the package installation will abort. If, on the other hand, the user had done the manual repair steps already, the export/import will succeed -- but in that situation the db files have already been converted, so the export/import cycle would not actually be needed.... If I'm correct, then it's probably better to leave the comparison as "lt-nl 2.4.23" (or perhaps "lt-nl 2.4.23-0ubuntu1"). That should guarantee that the export is being run using a pre-2.4.23 version of slapcat, and avoid touching the database on systems coming up from post-2.4.23 versions (since the script can't do anything for those systems anyway). 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs