Package: slapd
Version: 2.4.40-2
Severity: normal

Hi,

I wanted to manually set dumping to "never" before upgrading, because restoring
the dump breaks on partial replicas (#614569).  However, dpkg-reconfigure slapd
only asks if I want to "omit OpenLDAP server configuration", which I want, because
the replication config is hand made.  Thus I don't get to reconfigure dumping,
even though it has nothing to do with the server configuration itself.

Trying to upgrade with DEBIAN_PRIORITY=medium does not work either due to another
problem: I can switch off dumping then, and dumping is skipped all right, but the
reload is attempted regardless and fails not finding the dump.

On the other hand, I could be saved by a little additional logic.  #759597 may be
hard in general, but I use MDB, which does not need a dump/restore below 2.5,
which translates to never in Debian. :)

Control: tags -1 confirmed

If I'm reading correctly, the value of that choice isn't actually
important here: the problem is that the question about configuring
dumping is only presented on upgrade, not when (re)configuring a new or
existing installation.

http://anonscm.debian.org/cgit/pkg-openldap/openldap.git/tree/debian/slapd.config#n174

IMO, the dumping questions could be asked outside of that guard, even on
initial installation (and certainly on reconfiguration), with a low
priority.

That's a bug, for sure. dump_databases() exits early if dumping is
disabled, but the symmetric check in load_databases() is missing. That
doesn't make a lot of sense. :)

Ryan Tandy <ryan@nardis.ca> writes:

Agreed.

Also agreed.

Now, do you plan to do anything about these for jessie?  As I understand
it, anybody running a partial replica will necessarily hit this during
the wheezy -> jessie upgrade.  But we've still got a couple of days to
get an unblock for these fixes...