[Pkg-openldap-devel] Bug#621403: Bug#621403: Automatic upgrades for Berkeley DB version

[Ondřej Surý]

Steve,

I share your concern and I am not saying you should build-depend
openldap on libdb-dev, but that:

a) you could store the compiled-in version and compare it to used
version (and do the upgrade if they differ)

b) do the upgrade without dump&load, by running dbNEW_upgrade on them

That would solve the 'dpkg --compare-version "$2"
"version-in-unstable"' vs backported versions issue, which was brought
up on the debian-backports lists (aka if we backport openldap then the
upgrade from backports to next-stable will fail because the package
won't know it wants an upgrade).

O.

2011/5/13 Steve Langasek <vorlon at debian.org>:
> On Fri, May 13, 2011 at 01:58:15PM +0200, Ondřej Surý wrote:
>> I have prepared automatic Berkeley DB version upgrade script for sks,
>> if you want me to do something similar for openldap just ping me, it's
>> not a big deal after all :)
>
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=30;filename=sks_NMU.diff;att=1;bug=606183
>
>> (Or you can modify your debian/rules and postinst script yourself... ;)
>
> Nack.  Automatically upgrading to newer versions of BDB is not appropriate
> for OpenLDAP; OpenLDAP itself is too fragile to use arbitrary versions of
> BDB without vetting.
>
> --
> Steve Langasek                   Give me a lever long enough and a Free OS
> Debian Developer                   to set it on, and I can move the world.
> Ubuntu Developer                                    http://www.debian.org/
> slangasek at ubuntu.com                                     vorlon at debian.org
>



-- 
Ondřej Surý <ondrej at sury.org>
http://blog.rfc1925.org/