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

[Bill MacAllister]

--On Tuesday, November 25, 2014 04:08:36 PM +0100 Luca Bruno <lucab at debian.org> wrote:

> On Monday 24 November 2014 21:55:49 Ryan Tandy wrote:
>
>> So far I think I still like this idea better than the alternatives.
>
> Everybody loves hacks ;)
>
>> How would you feel about the backport using gnutls28? It's already
>> available in wheezy-backports with its dependencies. The benefit is that
>> it resolves #368297 and its various relatives; but the downside is that
>> installing libgnutls28 from wheezy-backports also pulls in newer nettle,
>> hogweed, and p11-kit libraries.
>
> I would say: let's go for gnutls28.
> Packages seem mostly updated and in synch with jessie, and we expect some
> issues when using the old ones. I don't think anybody will complain about
> pulling-in some more stuff from bpo.
>
>> Can you elaborate on "Cons: not future-proof" in your earlier message?
>
> Just that this is not a proper solution.  I am not aware of any
> issues rigth now, but if we later discover anything else
> related to DB versioning and dumping we would still have to come up with
> another solution. This is mostly a quickly workaround for this specific case.

If I understand correctly the issue is the ordering of the version
numbers to make sure that an distribution release of a package is not
superseded by a backported version of the same upstream version.
Russ Allbery taught us what I will call the tilde trick.  In his own
words:

   Any backported package, whether of our own unstable version of a
   package or a backport of Debian's unstable or testing version,
   should get a version number to allow clean upgrades to the unstable
   or testing version. This means using the ~ feature of Debian
   package versioning to give it an earlier version number. We do this
   by appending ~sbp, the two-digit version of Debian at which the
   backport is targetted, a +, and a version number corresponding to
   the revision of the backport. (sbp stands for Stanford backport.)

   For example, if we're backporting an unstable package with version
   number 2.2-4 to wheezy (Debian 7), the version number for the
   backport should be 2.2-4~sbp70+1. If we have to do a new backport
   of that same version to fix some bug, the next version is
   2.2-4~sbp70+2.

Bill

> Nonetheless, it looks like it's our better option at this moment, so let's go
> for it.
>
> Ciao, Luca



-- 

Bill MacAllister
Systems Programmer, Stanford University