Log in

19 November 2009 @ 04:29 pm
Why python2.6 is still not in unstable  

Getting python2.6 as the default ASAP is currently the #1 priority for the Python modules team. I also consider it very important and tried to help with it, but it is starting to get depressing.

The plan is to fix all packages in unstable to be compatible with python2.6 first. This would be easy if there hadn’t been a very badly planned change in the installation paths that came together. Because of it, quite a number of packages have to be fixed. Two months ago, I filed a lot of bugs in that order. I missed a number of issues, but overall, almost all packages have been fixed, thanks to Kumar Appaiah, Bastian Venthur and everyone else who sent patches and NMUs.

One of the biggest issues, though, comes from python-central. Since it doesn’t handle some of the new paths that were introduced (which is somehow ironic, since the python-central maintainer, Matthias Klose, is also the python maintainer who did this change), a large number of packages FTBFS when built against python2.6. In Ubuntu, it turned out to be a giant mess, most packages using python-central needing changes, and we wanted to avoid that. This is why Piotr Ożarowski sent a NMU for python-central that fixes these issues for good.

Guess what happened? Matthias Klose uploaded a new version that does not include the python2.6 fixes, completely discarding the work that has been done. And of course, making the upload of python2.6 to unstable, which was ready to be done in a few days, impossible.

I think it’s fine if Ubuntu maintainers don’t have the time to handle their packages in Debian. But it is clearly not acceptable to hold back development in Debian, nor to treat it as a garbage dumpster where you can send all the crappy software solutions that were badly designed in Ubuntu to duplicate them in Debian. This is what Matthias has been doing for several years. For how long are we going to tolerate such behavior? For how long will we leave such a critical package in the hands of a single person with no interest in Debian?

(Anonymous) on November 19th, 2009 03:56 pm (UTC)
That's not fair
Why you don't take over python package to python modules team? I think Debian Leader can take this decision, so it won't hurt anyone, because Matthias is ignoring everyone who has interest in python at Debian.
Jason D. Clintonjasondclinton on November 19th, 2009 04:24 pm (UTC)
Re: That's not fair
The response to every problem in FOSS is not "fix it your own damn self." We already have our plates full, thanks.
(Anonymous) on November 19th, 2009 04:46 pm (UTC)
No useful comment but I could not resist..
In ubuntu they even seem to forget they have python 2.6 already ;)

(Anonymous) on November 20th, 2009 08:05 am (UTC)
Re: No useful comment but I could not resist..
It's so funny to see they don't have a clue, but claim to have one by writing sophisticated changelog entries. :9
(Anonymous) on November 19th, 2009 05:49 pm (UTC)
NMU the package again?
(Anonymous) on November 20th, 2009 08:32 pm (UTC)
yes to another NMU
please, do! and do not delay it - just do it right, if others cannot do it properly :)
zwol on November 21st, 2009 03:06 am (UTC)
Maybe it's time to take this shit to the technical committee? I'm just a user, but I want 2.6 in squeeze, and this is getting ridiculous.
Kevin MarkKevin Mark [myopenid.com] on November 23rd, 2009 09:48 pm (UTC)
do what is right for Debian
Debian, when needed, has done things that were unpopular for others, but good for Debian:
1) iceweasel, etc.
2) schilly's cd software
3) put invariant section GFDL docs in non-free
and maybe others.
So the decision to apply a patch for Debian's benefit regardless of the maintainers wishes, seems the correct thing. If he disagrees, ask the TC and proceed from there.