Re: (again) Why default python is not 2.6 yet?

[Jakub Wilk]

* Sandro Tosi <mo...@debian.org>, 2010-02-17, 07:28:

Switching to 2.6 would mean that the packages currently FTBFSing can't
be used (with the default interpreter).

So, sorry, but yes, I think the FTBFSes are holding up the transition,
and for a good reason. Hopefully, I guess a few NMUs should do the
trick.

Ok, but those ~10 packages are only the tip of the iceberg. They were
scheduled weeks ago, and if they're still there, they'll probably last
longer. For example, are all the maintainers aware their packages are
FTBFS? I took 'gammu' as example, and there is no RC bug filed, so
probably Michael didn't even know gammu needs work.

How many packages will FTBFS, fail to start or to work, generate weird
errors or any other flavor of "won't work with 2.6"? Nobody knows,
that's why having the switch sooner than later gives us more time to
actually test the packages, let the users verify if they're working as
expected, and for developers (wide meaning) to fix any problem.

At the time of the switch, yes, the transition will start to grow,
given the current "hidden" bugs, but just waiting won't make them go
away/be fixed/noticed.

* Failures, which should be fixable by give-backs:

freej   mips
jppy    amd64 armel i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc
libiptcdata     mips
pytables        i386
python-biopython        alpha i386
python-chaco    alpha i386
python-ecore    armel mips
python-edbus    mips
python-edje     alpha
renpy   armel mips powerpc
twisted-runner  alpha amd64 armel i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel 
powerpc

* Temporary(?) dependency problems:

dballe/kfreebsd*
ifeffit
mapserver/mipsel
necpp/armel
openscap/kfreebsd*
pygpiv
python-jpype
python-kde3
sqlrelay

* Internal compiler errors:

polybori/sparc: #566242
pylucene/mips
syfi/mips
wxwidgets2.8/mips

* Other:

gammu: #567231
gnome-dvb-daemon: #569480
jppy/{alpha,ia64}: #558670

pyqwt3d/ia64
python-4suite: #569821
sagemath: #560558
xmms2/hppa: #558983



--
Jakub Wilk

I entirely concur. There's no reason this particular set of packages should stop us from switching to 2.6: many other packages *will* break after such a change. Anyway, I went through all the remaining build failures and triaged them: kdebindings: #566897 pivy/mipsel Besides, many packages haven't been compiled so far due to dep-waits and the fact the mips{,el} buildds are lagging behind the rest of the world.

signature.asc
Description: Digital signature