[pkg-kolab] Hacking slapd conffiles to fix an RC bug in kolabd (Was: Bug#596280: unblock: kolabd/2.2.4-20100624-2)

[Mathieu Parent (Debian)]

Hi Debian OpenLDAP Maintainers,

The recent move of slapd package to runtime config (aka cn=config, aka
slapd.d) unfortunately broke kolabd. After a bootstrap by the user,
kolabd manages some configuration files including slapd.conf. Since
slapd 2.4.23-3, this is broken as described in #595539.

I have proposed an hacky workaround which set slapd back to
slapd.conf. Julien as Release Team member (thank you!), waits an ack
for your team about this change. So: What do you think?

Note that kolabd for Wheezy will manage cn=config natively (most
probably by creating slapd.conf and using slaptest; but perhaps by
directly issuing ldap commands).

Regards

Mathieu Parent


PS : below is the unblock request

On Sat, Sep 11, 2010 at 9:28 PM, Julien Cristau <jcristau at debian.org> wrote:
> On Fri, Sep 10, 2010 at 00:26:24 +0200, Mathieu Parent wrote:
>
>> Please unblock package kolabd
>>
>> The main and only reason for this new version is to fix a bug
>> introduced by the move of slapd to runtime configuration (aka
>> cn=config, aka slapd.d). The fix includes a hack which is
>> against policy to revert a similar "against policy" change from
>> slapd postinst. Without this fix, kolab requires manual
>> intervention to work.
>>
>> The diff can be seen at http://svn.debian.org/wsvn/pkg-kolab/?op=comp&compare[]=%2F@1510&compare[]=%2F@1511
>>
>> The move back to static slapd config is done only if kolab
>> manages slapd.conf.
>>
>> unblock kolabd/2.2.4-20100624-2
>>
> I'm not unblocking this unless the openldap maintainers tell me it's ok.
>
> Cheers,
> Julien
>