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

2010-02-17 Thread Jakub Wilk
* Cyril Brulebois , 2010-02-17, 14:58: Jakub Wilk (17/02/2010): * Failures, which should be fixable by give-backs: jppyamd64 armel i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc twisted-runner alpha amd64 armel i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc I think I've g

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

2010-02-17 Thread Rene Engelhard
Hi, On Wed, Feb 17, 2010 at 04:18:28PM +0100, Sandro Tosi wrote: > On Wed, Feb 17, 2010 at 15:49, Rene Engelhard wrote: > > On Wed, Feb 17, 2010 at 12:05:56AM +0100, Sandro Tosi wrote: > >> If there is a valid, technical reason, please let us know, but as of > >> now I can't see any. > > > > Load

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

2010-02-17 Thread Sandro Tosi
On Wed, Feb 17, 2010 at 15:49, Rene Engelhard wrote: > On Wed, Feb 17, 2010 at 12:05:56AM +0100, Sandro Tosi wrote: >> If there is a valid, technical reason, please let us know, but as of >> now I can't see any. > > Loads of RC bugfixes (partly on obsolete versions) waiting to enter testing > whic

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

2010-02-17 Thread Rene Engelhard
Hi, On Wed, Feb 17, 2010 at 12:05:56AM +0100, Sandro Tosi wrote: > If there is a valid, technical reason, please let us know, but as of > now I can't see any. Loads of RC bugfixes (partly on obsolete versions) waiting to enter testing which would more blocked that it already is with the mips* bui

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

2010-02-17 Thread Cyril Brulebois
Jakub Wilk (17/02/2010): > * Failures, which should be fixable by give-backs: > > jppy amd64 armel i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc > twisted-runneralpha amd64 armel i386 kfreebsd-amd64 kfreebsd-i386 > mips mipsel powerpc I think I've given twisted-runner back sever

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

2010-02-17 Thread Jakub Wilk
* Sandro Tosi , 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,

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

2010-02-17 Thread Sandro Tosi
On Wed, Feb 17, 2010 at 11:31, Michal Čihař wrote: > Hi > > Dne Wed, 17 Feb 2010 07:28:58 +0100 > Sandro Tosi napsal(a): > >> 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

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

2010-02-17 Thread Michal Čihař
Hi Dne Wed, 17 Feb 2010 07:28:58 +0100 Sandro Tosi napsal(a): > 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 '

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

2010-02-17 Thread Jakub Wilk
* Sandro Tosi , 2010-02-17, 07:28: 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. FWIW, there is: http://bugs.debian.org/567231 -- Jakub Wilk signature.asc D