lasso_0.6.5-2.1_i386.changes is NEW [was: Re: removing python2.3]

2006-10-26 Thread Frederic Peters
I announced : > > python2.3-lasso (not yet converted?) > > In NEW queue. Matthias, why did you just upload a new version totally removing Python support ? I confess I missed 377800 and 380851 but this was *days* ago. I had been responsive on your previous email, why didn't you ask me ? Al

Re: removing python2.3

2006-10-23 Thread Ben Burton
Regarding decompyle again: > In that sense, I'd be happy to get it running under python2.4 instead > (i.e., running under python2.4 but decompiling python <= 2.3), and > assuming that works I'd suggest it stay in the archive for now. This is now done. I've just uploaded decompyle_2.3.2-4, which

Re: removing python2.3

2006-10-23 Thread Frederic Peters
Matthias Klose wrote: > python2.3-lasso (not yet converted?) In NEW queue. Frederic -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: removing python2.3

2006-10-23 Thread Ben Burton
> 1) removing packages only needed for python2.3: > ... > decompyle (2.3 only) Decompyle is a funny one, in that even though it only decompiles python2.3 bytecode, it remains useful as a disaster recovery tool after python2.3 has been removed. In that sense, I'd be happy to get it run

Re: removing python2.3

2006-10-22 Thread Raphael Hertzog
On Mon, 23 Oct 2006, Matthias Klose wrote: > With zope2.8 removed, the last package depending on python2.3 is gone, > so we are technically able to drop the support for python2.3. As > currently some packages have reverse dependencies on python2.3, > removing python2.3 without any

removing python2.3

2006-10-22 Thread Matthias Klose
With zope2.8 removed, the last package depending on python2.3 is gone, so we are technically able to drop the support for python2.3. As currently some packages have reverse dependencies on python2.3, removing python2.3 without any other action, would open new RC reports which doesn't seem