Transition to db5.3 (Was: Proposed transition to db5.2)
Since I haven't received any reaction at all and upstream has release
db5.3 meanwhile, I have uploaded db5.3 to unstable.
I would like to update db-defaults package to use db5.3 and remove
db5.1 from the wheezy[*]. I will do that in few days unless you stop me.
I think we have a plenty of time before freeze and hopefully we have
learned some lessons when transitioning from db4.8 to db5.1 (well
some maintainers seems to ignore me, but that won't change with db5.3)
* - and update transition bug, wiki pages, fill the bugs, NMU MIA packages,
you know the drill.
O.
On Wed, Dec 7, 2011 at 13:55, Ondřej Surý <ondrej@sury.org> wrote:
> Hi,
>
> I would like to discuss Berkeley DB transition again. Upstream has
> release bdb 5.2
> and since we still have about a year before next stable, it might be a
> good time to
> do the transition, so we keep up with upstream versions.
>
> db5.2 is already packaged in the experimental, and I wanted to keep it out of
> unstable, so people don't start to link with it, so we can control the
> damage which
> the introduction of new bdb usually causes.
>
> (Note: bdb 4.8 will probably stay for python2.x unless we find a way how to fix
> the regressions which the linking with newer bdb causes in the python builds.)
>
> Opinions, objections?
>
> O.
> P.S.: Please Cc: me.
> --
> Ondřej Surý <ondrej@sury.org>
--
Ondřej Surý <ondrej@sury.org>
Reply to: