Comment 6 for bug 574474
Revision history for this message
| joschi (jochen+launchpad-schalanda) wrote | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
I had the same problem upgrading slapd on Ubuntu 10.04 LTS.
Using a workaround (commenting out SLAPD_CONF in /etc/default/slapd and running `aptitude -f install`) I was able to make dpkg happy.
Generally it's IMHO a bad idea to do too much magic in the postinst script of the slapd package - at least if it breaks so easily.
> Obviously you will be likely to have the same problem again
> the next time slapd is upgraded... but I don't know if there
> will be any easy fix for that, given the general move away
> from slapd.conf-style configuration....
Unfortunately the new dynamic configuration (cn=config) is no viable alternative at the moment, as not all modules configuration is available through it (e. g. it's not possible to configure a meta backend using the new configuration style).