Re: How about a db 5.1.25 backport
Hi Andreas,
that seems like reasonable approach. But generally it would generally
affect only databases which uses transactional environment (the
database format hasn't changes since db 4.2) and that could be also
handled case by case.
F.e. you could also change openldap to save the current bdb version
into a on-disk file and do upgrade if the current format is changed
and not do comparison on debian version. That's what cyrus-imapd-2.*
packages do (see cyrus-common scripts). And I guess the openldap
maintainer could easily accept such patch.
O.
On Sun, Apr 17, 2011 at 13:46, Andreas Metzler
<ametzler@downhill.at.eu.org> wrote:
> Hello,
>
> I am considering uploading a backport of berkeley db 5.1.25. Packages
> in sid are (supposed to be) switching from 4.8 and later to 5.1, which
> is not available in squeeze, making backports hard.
>
> e.g. package foobar is switching to 5.1 in 3.1-2, its maintainer
> scripts check whether we are upgrading from <= 3.1-1 and upgrade to
> databases to the new file format in that case. If we uploaded
> 3.1-2~bpo60+1 linked against the older berkeley db stuff (and
> disabling the unnecessary upgrade magic) things would probably continue
> to work perfectly well in bpo. However upgrading to wheezy would be
> broken, since the db-upgrading scripts in the wheezy package won't be
> run (3.1-2~bpo60+1 is not <= 3.1-1)
>
> Any thoughts, what am I missing?
>
> cu andreas
> --
> `What a good friend you are to him, Dr. Maturin. His other friends are
> so grateful to you.'
> `I sew his ears on from time to time, sure'
>
--
Ondřej Surý <ondrej@sury.org>
http://blog.rfc1925.org/
Reply to: