[Pkg-openldap-devel] Package status

[Russ Allbery]

I now need to stop working on OpenLDAP packages and go work on other
things that are overdue (let's see if I manage to actually do that), but
2.3.35-2 as is currently in Subversion should be fine to upload.  I think
it's best to wait a bit to let 2.3.35-1 age first, and maybe migrate to
testing, before uploading given that none of the new fixes are
particularly exciting.

I added debugging packages for libldap-2.3-0 and slapd since we need them
for Stanford (we test a lot of cutting-edge stuff and regularly get core
dumps for which we need decent backtraces).  Hopefully that will be
uncontroversial.  It does mean that the next upload will need to sit in
NEW.

Additional bugs that I probably won't have time to address soon but which
should be reasonably straightforward and could be added to 2.3.35-2:

  #411413: slapd: Permit the use of the new configuration scheme
  #333428: slapd.schema.conf?

I'm still of mixed feelings about:

  #385898: slapd: add lsb logging

In general, I think using common output functions for all init scripts is
a good idea, but the current implementation is fairly dire, IMO, and I'm
afraid that switching to it now will decrease the quality of the init
script messages, particularly after errors.

I think:

  #375067: Running a second instance of slapd stops /etc/init.d/slapd stop
    from working

is because the PID file is overwritten, but I'm not sure the best solution
to the problem.

We should probably talk about whether it would help anything with all our
important bugs about SSL/TLS problems to add symbol versioning to libldap,
at least the 2.3 version (I don't really want to touch the 2.1 packages
very badly).

For 2.3.35-3, it would be good to look at our backward compatibility code
and upgrade support and consider removing anything that only applies to
versions of OpenLDAP from prior to oldstable.  In a quick look, I think
we're carrying a lot of that code around that could be dropped, along with
a bunch of debconf templates.  We should decide whether we're keeping
fix_ldif around as well.

I'd also like to revisit patches/use-lpthread and see if we can get rid of
it now by fixing whatever other bug made it necessary in the first place
(or observing that the bug is already fixed), since it's the only reason
right now why we have to run all the autotools during build.

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