Re: New python maintenance team
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 other teams like deb-scipy seem to just work. Just a quick note: I'm adopting python-xml as Zope team and I'll upload the package with the new maintainer soon (zope packages depends on it). -- Fabio Tranchitella <[EMAIL PROTECTED]>.''`. Proud Debian GNU/Linux developer, admin and user.: :' : `. `'` http://people.debian.org/~kobold/ `- _ 1024D/7F961564, fpr 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564 signature.asc Description: This is a digitally signed message part
Python 2.1/2.2 removal; Python 2.4 as default
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, like, before the weekend for example. As far as I can see, nothing really important depends on it any more, and whatever it is, can be NMUd or removed. Most if not all depending packages already have a bug filed for at least 2 months, which should've been plenty of warning. For reference, please find below the full list of packages that will be broken, only listing the first reason (often it's both build-dependencies and dependencies on all archs). If you want to help, and are not the maintainer of any python package needing changes yourself, you can do so right now, by starting to: 1) File bugs where there are no bugs filed yet, at serious 2) Upgrade any bugs that are already filed to 'serious' 3) Usertag such bugs, with debian-python@lists.debian.org as user, and 'python2.1', 'python2.2' respectively, for easier tracking. You can view these usertags by going to http://bugs.debian.org/usertag:debian-python@lists.debian.org 4) These packages are candidates for delayed NMUs immediately, and once python2.1/2.2 are removed they fall under the regular release team's 0-day NMU policy for RC bugs -- note that this policy includes that bugs need to be at least one week old, so there is not direct 0-day NMUing of previously non-RC-buggy packages. This shouldn't stop anyone from filing patches though, and assisting the maintainer where possible. 5) Or, as an alternative to (4), suggest removal of a package if that is appropriate. Do this by filing a bug on the package in question, and ask the maintainer to reassign to ftp.debian.org if he/she agrees. Now, for the list: carpaltunnel has an unsatisfied build-dependency: python2.2-dev decompyle2.2 has an unsatisfied build-dependency: python2.2-dev htmlgen has an unsatisfied build-dependency: python2.1-dev jabber.py has an unsatisfied build-dependency: python2.1 jython has an unsatisfied build-dependency: python2.1 libapache-mod-python has an unsatisfied build-dependency: python2.1-dev (>= 2.1.3-11) libapache-mod-python2.1 has an unsatisfied dependency on alpha: python2.1 libapache-mod-python2.2 has an unsatisfied dependency on alpha: python2.2 libapache2-mod-python has an unsatisfied build-dependency: python2.2-dev (>= 2.2.3) libapache2-mod-python2.2 has an unsatisfied dependency on alpha: python2.2 (>= 2.2.2) pexpect has an unsatisfied build-dependency: python2.2-dev pygdchart2 has an unsatisfied build-dependency: python2.1-dev pyopenssl has an unsatisfied build-dependency: python2.2-dev (>= 2.2) python-adns has an unsatisfied build-dependency: python2.1 python-cjkcodecs has an unsatisfied build-dependency: python2.1-dev python-crack has an unsatisfied build-dependency: python2.2-dev python-dhm has an unsatisfied build-dependency: python2.2-dev python-iconvcodec has an unsatisfied build-dependency: python2.1-dev python-japanese-codecs has an unsatisfied build-dependency: python2.2-dev python-korean-codecs has an unsatisfied build-dependency: python2.1-dev python-medusa has an unsatisfied build-dependency: python2.1-dev python-omniorb2 has an unsatisfied build-dependency: python2.1-dev python-orbit has an unsatisfied build-dependency: python2.1-dev python-oss has an unsatisfied build-dependency: python2.1-dev python-pam has an unsatisfied build-dependency: python2.1-dev python-pylibacl has an unsatisfied build-dependency: python2.2-dev python-pyxattr has an unsatisfied build-dependency: python2.2-dev python-weblib has an unsatisfied build-dependency: python2.1-dev python2.1-adns has an unsatisfied dependency on alpha: python2.1 python2.1-cjkcodecs has an unsatisfied dependency on alpha: python2.1 python2.1-gdchart2 has an unsatisfied dependency on alpha: python2.1 python2.1-htmlgen has an unsatisfied dependency on alpha: python2.1 python2.1-iconvcodec has an unsatisfied dependency on alpha: python2.1 python2.1-jabber has an unsatisfied dependency on alpha: python2.1 python2.1-korean-codecs has an unsatisfied dependency on alpha: python2.1 python2.1-medusa has an unsatisfied dependency on alpha: python2.1 python2.1-omniorb2 has an unsatisfied dependency on alpha: python2.1 python2.1-orbit has an unsatisfied dependency on alpha: python2.1 python2.1-oss has an unsatisfied dependency on alpha: python2.1 python2.1-pam has an unsatisfied dependency on alpha: python2.1 python2.1-tclink has an unsatisfied dependency on alpha: python2.1 python2.1-weblib has an unsatisfied dependency on alpha: python2.1 python2.2-adns has an unsatisfied dependency on alpha: python2.2 python2.2-cjkcodecs has an unsatisfied dependency on alpha: python2.2 python2.2-crack has an unsatisfied dependency on alpha: python2.2 python2.2-dhm has an unsatisfied dependency on
Re: New python maintenance team
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 > > > > team, but I'm looking forward to such a team. > > > Even though you may think you are not experienced enough, it seems you > > > just stepped forward and volunteered to lead this team. ;) I think > > > initiative is more important than knowing the ins and outs of Python. > > I do hope Matthias could lead such a team. He responded to my mail this > > morning. He didn't take a clear position about the team but he indicated > > that he would come with a proposal this week-end (and that he would also > > upload python2.5 in experimental). > > He would like to tie this transition with the new infrastructure for > > handling python modules. > [just realized that my mail did go to Raphael only, not intended] > Raphael, thanks for your interest. It's true that I did not respond to > emails ignoring our discussions from January and February on this very > list. It would be nice to build on these discussions for the > transition. Any news from your side? I think I did make it clear, > that we should get away from the transition system for all kind of > packages and implemented that (but side-tracked by other work in the > last month). Please expect an update from this at this weekend. 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 starting this transition the old, hard way that it's not to our advantage to continue postponing it due to the promise of better methods -- when those methods will still require sourceful uploads for the first round of implementation anyway. I think it's now been about a month since I suggested that we should focus on implementing the python infrastructure in a piece-wise manner in order to get this transition moving along; and still there's been no visible progress in that time, which makes that another month we could've used to start on this the hard way. :/ It would certainly be easier to do the transition using the new infrastructure, but that still blocks on having that infrastructure in place. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Re: Python 2.1/2.2 removal; Python 2.4 as default
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]>.''`. Proud Debian GNU/Linux developer, admin and user.: :' : `. `'` http://people.debian.org/~kobold/ `- _ 1024D/7F961564, fpr 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564 signature.asc Description: This is a digitally signed message part
Re: Python 2.1/2.2 removal; Python 2.4 as default
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. However, I've been unable to find a sponsor. Regards, Iustin Pop signature.asc Description: Digital signature
Re: Python 2.1/2.2 removal; Python 2.4 as default
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-built these two packages, removing 2.1 and 2.2 support > and adding 2.4. However, I've been unable to find a sponsor. If nobody else beats me to it, I'll sponsor you on monday. Ensure that the URL to your package is in the bug report filed on it regarding this transition, so that I, or whoever wants to look into this bug/package, can find it. This advice is valid for everyone, if you are a non-DD maintaining such package, make sure people can sponsor you instead of NMUing, without the need to ask first for URLs etc, by providing all necessary information in a bug. Thanks, --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber & MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Python 2.1/2.2 removal; Python 2.4 as default
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, removing 2.1 and 2.2 support > and adding 2.4. However, I've been unable to find a sponsor. Please don't hesitate to ask for sponsorship of python related modules here. Where can we find your packages ? BTW, there's no response in the BTS to these bug reports: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=351149 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=351150 Submitting in the BTS any relevant information, like availability of fixed packages, and the need for sponsor is always a good idea so that anyone else stumbling upon it could offer you his help. Maybe Matthias himself could have sponsored your upload since he reported the bug ... :-) Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Python 2.1/2.2 removal; Python 2.4 as default
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 PROTECTED]
Re: New python maintenance team
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 too many things are depending on it now. If some new framework is developed, it will take several months before it is used in enough packages to be useful, and several more months is too much. -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom
Re: New python maintenance team
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 -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 too > many things are depending on it now. If some new framework is developed, > it will take several months before it is used in enough packages to be > useful, and several more months is too much. signature.asc Description: Questa è una parte del messaggio firmata digitalmente
Re: Python 2.1/2.2 removal; Python 2.4 as default
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 information. Thanks, Iustin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: New python maintenance team
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 time to suggest those maintainers to join the team and integrate their packages. I'll try to finish the documentation and make an announce this WE if possible. For the maintenance of the core python packages, Matthias is the Maintainer and even if there's a pkg-python Alioth project, he hasn't yet started to use it. Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: New python maintenance team
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 Alioth project and an associated SVN repository. Right now it's empty but Matthias will start using it this week-end (if all goes well). http://alioth.debian.org/projects/pkg-python/ http://svn.debian.org/wsvn/pkg-python/ Given that 5-6 persons volunteered, Matthias probably won't give write access to everybody directly. So the right course of action is to make use of the Package Tracking System to subscribe to the various python source packages: http://packages.qa.debian.org/p/python-defaults.html http://packages.qa.debian.org/p/python2.4.html http://packages.qa.debian.org/p/python2.3.html And start helping out by submitting patches to the BTS, by forwarding bugs upstream, doing bug triaging and so on. After some time I'm confident that Matthias will add you to the Alioth project. Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
new future inside_
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, 206-202-2033 TTYL, Joey Sousa
Re: New python maintenance team
> 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 starting this transition the old, hard way that it's > not to our advantage to continue postponing it due to the promise of better > methods -- when those methods will still require sourceful uploads for the > first round of implementation anyway. FWIW, seconded. Please just upload python2.4 as the default python version. We have enough time get the infrastructure in place and attempt the automated transition for python2.5. Ganesan -- Ganesan Rajagopal (rganesan at debian.org) | GPG Key: 1024D/5D8C12EA Web: http://employees.org/~rganesan| http://rganesan.blogspot.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
