[pkg-db-devel] Bug#675611: Bug#675611: libdb5.1-dev: no way to install libdb4.x-dev in parallel

[Ondřej Surý]

On Sun, Jun 3, 2012 at 12:34 AM, Toni Mueller <support at oeko.net> wrote:
> Hi,
>
> On Sat, Jun 02, 2012 at 11:30:30PM +0200, Ondřej Surý wrote:
>> Isn't python 2.6 going away? I have just removed libdb4.8-dev in a
>
> I'm not sure, but argued against that on the python list
> (debian-python at l.d.o). [1]

So, what is the conclussion?  Should I care about libdbX.Y for python2.6
or not?

>> If python2.6 isn't actually going away (e.g won't be released in
>> wheezy), we have to decide what to do about db4.8 - I would really
>> like to drop the library and development files and just keep
>> db4.8-util for database file upgrades. There is also a problem that db
>> files created by python would be incompatible with the rest of the
>> other packages.
>
> Of course, but if Python2.6 could be made to work with libdb5.1, or just
> do that out of the box, I would not bother about libdb4.8 - I only don't
> have enough expertise to answer the question. In that case, having an
> entry in NEWS.Debian would be sufficient, imho.

Well, I have usually took standalone berkeley db python package and
prepared patch on top of python2.x version to support newer berkeley
db version.

I could do that again if really needed, but I would like to hear the
maintainer and/or release team voice first.

The db4.7+db4.8->db5.1 transition is almost finished, with the one
exception and that is python2.6. (Not counting broken upload of nmh.)

http://release.debian.org/transitions/html/libdb.html

and status from dak:

Checking reverse dependencies...
# Broken Depends:
clisp: clisp-module-berkeley-db [hurd-i386] # blocked by FTBFS on hurd
cyrus-imapd-2.4: cyrus-common # only db4.8-utils needed, thus OK
db-defaults: db-upgrade-util # only db4.8-utils needed, thus OK
python2.6: python2.6
           python2.6-dbg

# Broken Build-Depends:
clisp: libdb4.8-dev # blocked by FTBFS on hurd-i386
python2.6: libdb4.8-dev

Dependency problem found.

O.
-- 
Ondřej Surý <ondrej at sury.org>