[Pkg-openldap-devel] Upgrades fail due to checkpoint directive

[Quanah Gibson-Mount]

--On Thursday, January 10, 2008 5:53 PM -0800 Russ Allbery <rra at debian.org> 
wrote:

> Steve Langasek <vorlon at debian.org> writes:
>
>> I don't understand why upstream would want to disallow setting global
>> defaults for the BDB backend, but anyway, here's a stab at migrating the
>> option from the backend config to the per-db config.  It's based closely
>> on the existing write_slapd_conf function, but unfortunately that wants
>> a regexp which isn't practical here so that function can't be used
>> directly.
>>
>> Known flaw, if there's already a 'checkpoint' database directive in
>> place you'll now have two of them; but I think the last listed takes
>> precedence anyway so shouldn't have any practical effects.
>
> Yeah, that should be fine, I think.
>
>> Are we sure the 'checkpoint' option is the only one whose semantics have
>> changed?  There are quite a few other options listed in slapd-bdb(5), I
>> don't know whether any of them were allowed in the 'backend' config
>> before.  Well, easy enough to drop in handling for any other options we
>> need to shuffle around.
>
> I expect there may be others, but checkpoint was the only one that we
> wrote out ourselves.

So to be more precise:

backend <XXX>

noted the start of a section related to the configuration for all databases 
of that type.  However, that ability was never actually implemented.  So 
all options in slapd-bdb, etc, still apply, but they must be contained 
inside a database <xxx> definition.  I.e., you can't globally apply an 
option type to all subsequent databases of that type (which was the 
original intention) as it was never implemented.  OpenLDAP 2.4 notes this 
as a misconfiguration, as it must be able to fully change the database over 
to cn=config format.

--Quanah


--

Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra ::  the leader in open source messaging and collaboration