Re: Package adoptions
On Mon, 2013-02-18 at 19:34 +, Javi Merino wrote: > On Mon, Feb 18, 2013 at 05:24:34AM +0800, Thomas Goirand wrote: > > On 02/18/2013 04:43 AM, Vincent Bernat wrote: > > > I am currently too short on time to do anything but I have high interest > > > in both setproctitle and gevent and therefore if nobody steps in, I will > > > maintain them under the DPMPT. I could also take python-greenlet since > > > it seems in good shape. > > I may help as well with python-greenlet if needed. It's a dependency for > > ceilometer, cinder, heat, keystone and nova... > > Please note that python-greenlet is currently maintained by Laszlo > Boszormenyi[0] (cced) so if you guys are interested in it, you should > contact him. Sorry, I was away for some days. I'm a DD and as Javi notes, I maintain python-greenlet. I was taking steps to get over on the other, mentioned packages as well. I've half-ready/odobted packages and would like to maintain them. Regards, Laszlo/GCS signature.asc Description: This is a digitally signed message part
Re: How does team maintenace of python module works?
On 18 February 2013 22:23, Ludovic Gasc wrote: > I propose to make a poll on the Web (Doodle or other) and ask the question > in another thread, I'm not sure that each subscriber has read this long > thread. > I don't think I'll do that myself - the responses I have seen don't have even the barest hint of consensus, and there's no particular reason to think that a wider sample would produce a more unified opinion. If you think it would be useful, though, I shan't stop you doing it. Thomas
Re: How does team maintenace of python module works?
* Ludovic Gasc , 2013-02-18, 23:23: I propose to make a poll on the Web (Doodle or other) and ask the question in another thread, I'm not sure that each subscriber has read this long thread. And then, if the results are still unsatisfactory, let's create a repo at GitHub and let people vote via pull requests. (SNCR) -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130218223243.ga5...@jwilk.net
Re: How does team maintenace of python module works?
On Mon, Feb 18, 2013 at 11:08 PM, Thomas Kluyver wrote: > On 18 February 2013 20:46, Ludovic Gasc wrote: > >> I vote D, and I can handle the migration from SVN to Git, I've done this >> several times for my work and WYMeditor. >> >> Are you interested? >> > I'm interested personally, but the votes so far suggest there's no real > will for any change - the only option with more than one first preference > vote is the status quo. > I propose to make a poll on the Web (Doodle or other) and ask the question in another thread, I'm not sure that each subscriber has read this long thread. > > > Thomas >
Re: How does team maintenace of python module works?
On 18 February 2013 20:46, Ludovic Gasc wrote: > I vote D, and I can handle the migration from SVN to Git, I've done this > several times for my work and WYMeditor. > > Are you interested? > I'm interested personally, but the votes so far suggest there's no real will for any change - the only option with more than one first preference vote is the status quo. Thomas
Re: How does team maintenace of python module works?
On Feb 16, 2013 1:43 PM, "Thomas Kluyver" wrote: > > On 16 February 2013 09:10, Thomas Goirand wrote: >> >> It would be really stupid to only want to "claim" to be working as part >> of the team, that's not at all what I want to do. I'd like to be able to >> help when I can, and receive help when I need, which is the point of a team. > > > I agree there are reasonable reasons to want to maintain something in git, and it's not ideal to exclude those packages from team maintainership just because of the VCS question. Although, if it came to that, the team would be happy to offer advice and assistance for Python packages that aren't maintained by the team. We all want stuff to work smoothly, whether or not it's "our" stuff. > > I suggest we take a poll - not as a binding decision, but to get an idea of the level of support for different courses of action. You're free to attach more weight to the votes of highly involved team members. > > The following four positions have all been advocated in this thread: > > A - Maintain the status quo, in which DPMT packages may only be maintained in SVN. > B - As A, but encourage the creation of a separate team where Python modules can be maintained in git. > C - Allow DPMT-maintained packages to live in SVN or git, so new packages can be committed to git if the packager prefers. Optionally, we could make provisions to migrate existing packages. > D - Migrate all the DPMT-maintained packages to git. > > (I suggest we don't consider other VCSs - while we might have our favourites, I sampled the list of Debian teams, and found very few using anything other than svn or git. So tools & workflows for other VCSs are likely to be less well developed.) I vote D, and I can handle the migration from SVN to Git, I've done this several times for my work and WYMeditor. Are you interested? > > So I would vote CDBA, in order of preference. > > Thanks, > Thomas
Re: How does team maintenace of python module works?
* Piotr Ożarowski , 2013-02-14, 23:49: I (as an admin) will (and already did in the past) ask anyone who doesn't keep a team package in SVN to remove DPMT/PAPT from Maintainer/Uploaders (until we officially migrate to something else). Please start with these (they declare Vcs-Git): bugz dajaxice django-dajax polib pyjavaproperties python-kyotocabinet python-pgpdump wokkel and these (they don't use any VCS, AFAICS): python-reportlab python-w3lib -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130218203608.ga5...@jwilk.net
Re: Package adoptions
On Mon, Feb 18, 2013 at 05:24:34AM +0800, Thomas Goirand wrote: > On 02/18/2013 04:43 AM, Vincent Bernat wrote: > > ❦ 4 février 2013 20:00 CET, Örjan Persson : > > > >> I don't have the time to maintain my packages anymore. I just wanted to > >> check with you guys first if you're interested in adopting the packages > >> before I RFA them. The packages are python-setproctitle[1], > >> python-greenlet[2] and python-gevent[3]. > >> > >> [1] https://github.com/op/pkg-python-setproctitle > >> [2] https://github.com/op/pkg-python-greenlet > >> [3] https://github.com/op/pkg-python-gevent > > I am currently too short on time to do anything but I have high interest > > in both setproctitle and gevent and therefore if nobody steps in, I will > > maintain them under the DPMPT. I could also take python-greenlet since > > it seems in good shape. > I may help as well with python-greenlet if needed. It's a dependency for > ceilometer, cinder, heat, keystone and nova... Please note that python-greenlet is currently maintained by Laszlo Boszormenyi[0] (cced) so if you guys are interested in it, you should contact him. [0] http://packages.debian.org/sid/python-greenlet Cheers, Javi signature.asc Description: Digital signature
Re: RFR: python-qrcode -- native python module to generate QR codes
Hello, I uploaded a reworked version of python-qrcode. * Package name: qrcode Version : 2.4.2-1 Upstream Author : Lincoln Loop * URL : https://github.com/lincolnloop/python-qrcode * License : BSD (2 clause) MIT/X11 (BSD like) Section : python http://mentors.debian.net/debian/pool/main/q/qrcode/qrcode_2.4.2-1.dsc It builds those binary packages: python-qrcode - QR Code image generator The package and further information can be accessed here. http://mentors.debian.net/package/qrcode Again happy for any feedback. Thanks a lot and kind regards Cornelius signature.asc Description: OpenPGP digital signature
Re: RFR: python-qrcode -- native python module to generate QR codes
Am 18.02.2013 15:59, schrieb Jakub Wilk: > * Cornelius Kölbel , 2013-02-17, 13:46: >> thanks a lot for your feedback. I think I took care of all your >> comments - although I was not able to run your lintian4py. > > Out of interest, why? > >> Should I increase the version to 2.4.2-2 or is this version only >> increased, _after_ a package is released? > > I believe most sponsors prefer the latter. OK, lintian --pedantic produced no error, lintian4py --pedantic produced: p: python-qrcode: pyflakes-unused-import usr/share/pyshared/qrcode/__init__.py:1: make p: python-qrcode: pyflakes-unused-import usr/share/pyshared/qrcode/__init__.py:3: image How pedantic should be be? ;-) Kind regards Cornelius signature.asc Description: OpenPGP digital signature
Re: RFR: python-qrcode -- native python module to generate QR codes
Am 18.02.2013 16:16, schrieb Andrey Rahmatullin: > On Mon, Feb 18, 2013 at 04:09:27PM +0100, Cornelius Kölbel wrote: >> What would be your recommended way to install/use lintian4py? > You need a sid system in some form to build and test packages for sid > anyway so it's not a big problem. > thx, will do so. signature.asc Description: OpenPGP digital signature
Re: RFR: python-qrcode -- native python module to generate QR codes
On Mon, Feb 18, 2013 at 04:09:27PM +0100, Cornelius Kölbel wrote: > >> thanks a lot for your feedback. I think I took care of all your > >> comments - although I was not able to run your lintian4py. > > > > Out of interest, why? > I am running a squeeze system here and was not able to install the > package from experimental due to to many version conflicts. > > Fetching the sources, I "Can't locate Monkey/Patch.pm" and I also did > not find a perl module in the default debian repos to match this. > > What would be your recommended way to install/use lintian4py? You need a sid system in some form to build and test packages for sid anyway so it's not a big problem. -- WBR, wRAR signature.asc Description: Digital signature
Re: RFR: python-qrcode -- native python module to generate QR codes
Hi Jabuk, Am 18.02.2013 15:59, schrieb Jakub Wilk: > * Cornelius Kölbel , 2013-02-17, 13:46: >> thanks a lot for your feedback. I think I took care of all your >> comments - although I was not able to run your lintian4py. > > Out of interest, why? I am running a squeeze system here and was not able to install the package from experimental due to to many version conflicts. Fetching the sources, I "Can't locate Monkey/Patch.pm" and I also did not find a perl module in the default debian repos to match this. What would be your recommended way to install/use lintian4py? Thanks a lot Cornelius signature.asc Description: OpenPGP digital signature
Re: RFR: python-qrcode -- native python module to generate QR codes
* Cornelius Kölbel , 2013-02-17, 13:46: thanks a lot for your feedback. I think I took care of all your comments - although I was not able to run your lintian4py. Out of interest, why? Should I increase the version to 2.4.2-2 or is this version only increased, _after_ a package is released? I believe most sponsors prefer the latter. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130218145910.ga8...@jwilk.net
Bug#700842: ITP: python-wsgilog -- WSGI logging and event reporting middleware
Package: wnpp Severity: wishlist Owner: Mike Gabriel * Package name: python-wsgilog Version : 0.3 Upstream Author : L. C. Rees * URL : http://pypi.python.org/pypi/wsgilog/ * License : BSD Programming Lang: Python Description : WSGI logging and event reporting middleware Supports logging events in WSGI applications to STDOUT, time rotated log files, email, syslog, and web servers. Also supports catching and sending HTML-formatted exception tracebacks to a web browser for debugging. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130218095251.5769.8233.report...@minobo.das-netzwerkteam.de
