[Pkg-openldap-devel] Backporting slapd out of jessie to wheezy possible?

[Ryan Tandy]

On Sat, Nov 15, 2014 at 08:07:48PM +0100, Luca Bruno wrote:
>This is probably too late, yes.
>However we can later discuss if we can/want/should move to some libmagic-based
>detection (or similar) for the future.

Libmagic is an interesting idea. I didn't know it understood DB files. 
My previous ideas about this were mostly along the lines of dropping an 
information file in /var/lib/slapd and checking it during upgrades.

On the other hand IIUC this is likely to be the last libdb transition, 
so it may not be worth the effort at this point.

> * override slapd/dump_database=always in bpo packages
>   Cons: this permanently overrides admin choice, is subpar and still requires
>         some packaging work for bpo

Frankly, I'm not enthusiastic about that idea. :)

> * play dirty tricks with version numbering
>   Cons: not future-proof, we will end up we silly numbers like
>         "2.4.31+really2.4.40"
>
>(The "+really" is normally used to recover from versioning screw-ups.)

I also thought of this, after sending my previous message. The version 
number does look silly, but it's also a minimally invasive way of 
getting the result we want, if bpo-ftpmasters accept it.

I tested this quickly, using the version 
'2.4.31+really2.4.40-2~wheezy1'. The check for << 2.4.39-1 does cause a 
spurious db reload on upgrade from wheezy to wheezy-bpo; but more 
importantly, the upgrade from wheezy-bpo to jessie does work properly.