This bug is related to to LP: #632051. The two are triggered by a different specific issue within the slapd.conf file, and would need different changes to the postinst script in order to allow it to actually parse the config file correctly... but I think the patch I proposed in that bug would allow the package upgrade to complete, with a warning message, in both situations (rather than aborting and leaving the package in an unconfigured state, as currently happens in both situations).
This bug is related to to LP: #632051. The two are triggered by a different specific issue within the slapd.conf file, and would need different changes to the postinst script in order to allow it to actually parse the config file correctly... but I think the patch I proposed in that bug would allow the package upgrade to complete, with a warning message, in both situations (rather than aborting and leaving the package in an unconfigured state, as currently happens in both situations).