[Pkg-openldap-devel] Bug#596100: When told not to initially configure slapd, (un-)installation fails due to init script return code.

[Matthew King]

Steve Langasek <vorlon at debian.org> writes:

>> 1) Creating /etc/ldap/noslapd as part of the postinst which the administrator
>>    can remove when slapd is configured.
>
> I don't consider this appropriate.  If you ask not to automatically
> configure slapd, then the package is not usable until manual action is taken
> and we should not mark the package as "installed".

I don't recall coming across that before. Other packages which give the
option not to have debconf do configuration don't break dpkg when they
do it, eg. postfix. I'm not sure how that works - maybe it just doesn't
try to start the daemon in the postinst.

In my case, slapd is (will be) installed with chef - the recipe must set
the no_configuration flag and then configure chef after the package is
installed, however if dpkg fails, the recipe will also fail and will
never proceed to the configuration stage. Catch 22.

Matthew

-- 
I must take issue with the term "a mere child", for it has been my
invariable experience that the company of a mere child is infinitely
preferable to that of a mere adult.
                                           --  Fran Lebowitz