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

[Russ Allbery]

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.

I hadn't yet had a chance to check with upstream on whether this was
intentional.

Also, I did check on the libldap vs. libldap_r thing, but I haven't gotten
any response.

-- 
Russ Allbery (rra at debian.org)               <http://www.eyrie.org/~eagle/>