Re: New python maintenance team

2006-04-07 Thread Ganesan Rajagopal
> Steve Langasek <[EMAIL PROTECTED]> writes: > I think everyone is agreed that we want greater automization of python > transitions, but the longer this is postponed, the more problematic this > becomes for etch. It's my impression that there is enough untapped manpower > available to work on

new future inside_

2006-04-07 Thread Basil N. Hancock
How are you, A Gen_uine Coll`ege Deg.ree in 2 weeks Cal_l us now_!-> 206-202-2033 Within 2 weeks! No Study Required!   1_0_0_% Veri.fiable! Right now the following deg.rees are being offered: B/A,   .B/S/C,   .M/A,.M/S/C,.M/B/A,   .P/H/D, C.al_l us now_ for more information, 2

Re: New python maintenance team

2006-04-07 Thread Raphael Hertzog
On Thu, 06 Apr 2006, Raphael Hertzog wrote: > Hello everybody, > > I'm not experienced enough with Python to lead such a maintenance > team, but I'm looking forward to such a team. > > Who would be interested to help ? OK, thanks to everyone who volunteered so far. There's already a pkg-python

Re: New python maintenance team

2006-04-07 Thread Raphael Hertzog
On Fri, 07 Apr 2006, Marco Cabizza wrote: > Can we have an Alioth group created? And a TODO list, possibly, so that > as we are already more than just "two guys" we can start working on > something :) There's already a python-modules Alioth project and during the BSP next week, it may be a good ti

Re: Python 2.1/2.2 removal; Python 2.4 as default

2006-04-07 Thread Iustin Pop
On Fri, Apr 07, 2006 at 01:38:43PM +0200, Iustin Pop wrote: > I've already re-built these two packages, removing 2.1 and 2.2 support > and adding 2.4. However, I've been unable to find a sponsor. Thanks everyone for the suggestions. Will update the bug reports later today with the relevant informa

Re: New python maintenance team

2006-04-07 Thread Marco Cabizza
I fully agree with Joss. Can we have an Alioth group created? And a TODO list, possibly, so that as we are already more than just "two guys" we can start working on something :) ~marco Il giorno ven, 07/04/2006 alle 14.11 +0200, Josselin Mouette ha scritto: > Le vendredi 07 avril 2006 à 03:35 -0

Re: New python maintenance team

2006-04-07 Thread Josselin Mouette
Le vendredi 07 avril 2006 à 03:35 -0700, Steve Langasek a écrit : > I think everyone is agreed that we want greater automization of python > transitions, but the longer this is postponed, the more problematic this > becomes for etch. I can only agree. The move to python 2.4 is an urgent matter, as

Re: Python 2.1/2.2 removal; Python 2.4 as default

2006-04-07 Thread Matthias Klose
Jeroen van Wolffelaar writes: > The first freezes are already closing in fast, did I miss something? There's no update since http://lists.debian.org/debian-devel-announce/2005/10/msg4.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL

Re: Python 2.1/2.2 removal; Python 2.4 as default

2006-04-07 Thread Raphael Hertzog
On Fri, 07 Apr 2006, Iustin Pop wrote: > On Fri, Apr 07, 2006 at 12:33:11PM +0200, Jeroen van Wolffelaar wrote: > > python-pylibacl has an unsatisfied build-dependency: python2.2-dev > > python-pyxattr has an unsatisfied build-dependency: python2.2-dev > > I've already re-built these two packages,

Re: Python 2.1/2.2 removal; Python 2.4 as default

2006-04-07 Thread Jeroen van Wolffelaar
On Fri, Apr 07, 2006 at 01:38:43PM +0200, Iustin Pop wrote: > On Fri, Apr 07, 2006 at 12:33:11PM +0200, Jeroen van Wolffelaar wrote: > > python-pylibacl has an unsatisfied build-dependency: python2.2-dev > > python-pyxattr has an unsatisfied build-dependency: python2.2-dev > > I've already re-buil

Re: Python 2.1/2.2 removal; Python 2.4 as default

2006-04-07 Thread Iustin Pop
On Fri, Apr 07, 2006 at 12:33:11PM +0200, Jeroen van Wolffelaar wrote: > python-pylibacl has an unsatisfied build-dependency: python2.2-dev > python-pyxattr has an unsatisfied build-dependency: python2.2-dev I've already re-built these two packages, removing 2.1 and 2.2 support and adding 2.4. How

Re: Python 2.1/2.2 removal; Python 2.4 as default

2006-04-07 Thread Fabio Tranchitella
On Fri, 2006-04-07 at 12:33 +0200, Jeroen van Wolffelaar wrote: > zopeinterface has an unsatisfied build-dependency: python2.2-dev This package can be removed, pythonX-zopeinterface are now built from zope3 source package. -- Fabio Tranchitella <[EMAIL PROTECTED]>.''`. P

Re: New python maintenance team

2006-04-07 Thread Steve Langasek
On Thu, Apr 06, 2006 at 07:11:31PM +0200, Matthias Klose wrote: > Raphael Hertzog writes: > > On Thu, 06 Apr 2006, Sebastian Rittau wrote: > > > Am Donnerstag, den 06.04.2006, 09:58 +0200 schrieb Raphael Hertzog: > > > > I'm not experienced enough with Python to lead such a maintenance > > > > tea

Python 2.1/2.2 removal; Python 2.4 as default

2006-04-07 Thread Jeroen van Wolffelaar
Hi all, It's been quite a while, but 2.1 and to a slightly lesser extend, 2.2 are really obsolete now. One of the issues with 2.1 and 2.2 are that they don't build on amd64, and are holding up a whole chain of packages also. Therefore, I'd like to remove python 2.1 and 2.2 as soon as possible, li

Re: New python maintenance team

2006-04-07 Thread Fabio Tranchitella
On Thu, 2006-04-06 at 19:11 +0200, Matthias Klose wrote: > I'm sure one or more teams could be useful, packagers should be able > to decide on their own if they want to join a team. There are lot of > packages, where people did ask for maintainance (i.e. python-xml), but > got no response. On the