2011/4/15 Matthias Klose <d...@debian.org>: > On 04/14/2011 04:06 PM, Ondřej Surý wrote: >> >> Package: python2.6 >> Version: 2.6.6-8 >> Severity: normal >> >> Attached is patch for db5.1 usage. > > For now, I will stay with db4.8 for python2.6 and python2.7. First, lets > get 2.7 a supported python version,
Done in python-defaults 2.6.6-14, python2.7 transition is also done according to transition tracker[1]. > then check current build results with db4.8 What do you mean by that? > then see if there a regressions with 5.1 in an upload to > experimental. There were not any reported regression when other packages migrated to db5.1. I have also checked the upstream of bsddb and I didn't saw anything which might be source of regression. Is there anything in particular Please bear in mind that any database created with python bsddb will be incompatible with the rest of whole Debian, which is not the situation anybody wants. I would also like to point out that I did create a transition and future plan[2] for Berkeley DB packages which include only one version of dbX.Y in the stable release and two versions of tools oldstable and stable to allow. I have sent the plan to debian-release and debian-devel and haven't heard any objections against that plan. It would be most unfortunate if the python would not keep up with the rest of the archive since I plan to remove libdb4.7-dev and libdb4.8-dev from the archive sometime this year (with libdb4.7-dev coming first probably before vacation and libdb4.8-dev coming sometime in the autumn/winter). 1. http://release.debian.org/transitions/html/python2.7.html 2. http://wiki.debian.org/BerkeleyDB O. -- Ondřej Surý <ond...@sury.org> http://blog.rfc1925.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
