Re: Bug#746741: release.debian.org: dh-python2 transition
On Tue, May 27, 2014 at 10:59:56PM +0200, Emilio Pozuelo Monfort wrote: > On 05/05/14 15:46, Julien Cristau wrote: > > On Sat, May 3, 2014 at 07:48:03 +0100, Dimitri John Ledkov wrote: > >> Debian python teams would find useful to evaluate on continuous basis > >> removal of python-support from the archive and thus migrating to > >> dh-python2. We are uncertain of the scope, and the pace at which this > >> transition can be completed. But it would be extremely useful to have a > >> transition tracker setup (permanent-type ?!). > >> > > I don't think that makes much sense as a transition / tracker, as it's > > not something rebuilds would fix or where it's hard to find the set of > > affected packages. > > FWIW, you may get a lot of things switched by emailing debian-devel@ with a > dd-list. And also by adding a lintian check. I'm currently undergoing a sprint to push this to an end, I'm down to ~80 packages still affected, a handful already in deferred, and if I continue with this pace I'm going to NMU/team upload all of them by the end of the next week or so. We came to a point where I think the number of affected packages is not going down by itself, since most of the packages have either the maintianer that is de-facto MIA or the package is de-facto orphaned. So I ask for permission to bump all those bugs to severity:serious, and move on; that way I'll have the excuse to ask for RM: RoQA for a couple of packages without feeling too guilty... PS: let me guess, should this bug be reassigned to ftp-master for RM? since you already stated -release is not the right place for this, and a transition tracker is not really needed in this case. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Request to join
I would like to join the python modules team. I am currently working on packaging sklearn-pandas, which I would like to maintain as part of the team. I am also interested in getting involved in general maintenance of team packages. I have read an accept https://python-modules.alioth.debian.org/policy.html. My alioth login is cbaines-guest. Thanks, Chris
Request to join the DPMT team
Hi, I want to join the DPMT team. My main goal is to help to maintain some packages which I maintain upstream. For example, the python-kiwi package. It is very outdated on Debian and when I contacted its maintainer he said that I should fell free to takeover the maintainership and to contact someone from the DPMT team to sponsor my upload. I'm already familiar with packaging as I'm currently maintaining a PPA used to deploy Stoq [1], an open source retail system that is developed by the company I work (Async Open Source). Not only I package new versions of stoq and its dependencies that we develop (python-kiwi, stoqdrivers), but I also package some python libraries that are not in the official Ubuntu repositories. For example, weasyprint, python-tinycss and python-pyphen which I packaged from scratch, and others like python-cssselect which I backported from debian itself. Those which I packaged from scratch I want to upload to upload to debian too. Btw, I'm Debian testing/sid user since 2011. I have read the DPMT policy page [2] and I accept it. My alioth login is 'hackedbellini-guest'. I just created it. Please let me know how should I proceed now. [1] https://launchpad.net/~stoq-dev/+archive/ubuntu/lancamentos [2] http://python-modules.alioth.debian.org/policy.html#joining-the-team -- Thiago Bellini Ribeiro http://hackedbellini.org PGP: D70FD60E “Real knowledge is to know the extent of one's ignorance.” - Confucius
removing p9m4 from PAPT
I'm in the process of NMUing/QA upload p9m4 for the python-support removal, and noticed #740323 from the MIA team. Given that looks like nobody is interested in it, shall I do a QA upload of the package kicking it out of the team? If that the case, please remove the svn repo or mark it as old/deprecated (=> I'm not in the PAPT team, and anyway I don't know how the python teams deal with packages going out of the team (whether there is an attic or such. If that was in git I'd have just cp the repository to collab-maint, but with svn...). I'll wait some time to hear from you before uploading. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
