I will try to actually run a test of this scenario sometime in the next
few days, but at first glance it appears to me that simply adding "{1}"
to both the "grep" and the "sed" lines of the postinst script will fix
Hardy -> Lucid upgrades, but will cause new problems for other upgrade
paths.
In particular, if the slapd package was upgraded 2.4.17/2.4.18
timeframe, an oldAccess line without any index would have already been
added to the .ldif file, and then upon upgrade to Lucid, this updated
postinst script would add the new "{1}" version of the line as well....
--
slapd package configuration aborts due to "ordered_value_sort failed on attr
olcAccess" error during Hardy -> Lucid upgrade
https://bugs.launchpad.net/bugs/538516
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
