Joining DPMT and PAPT
Hi I want to join both teams to maintain my python packages under their umbrella. Currently they are under the Debian salsa group. My salsa login is gfa I accept both policies (with Yao and Ondřej's updates in MRs) https://salsa.debian.org/python-team/tools/python-apps/blob/master/policy.rst https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst I'll update the packages to match the team(s) policy -- IRC: gfa GPG: 0X44BB1BA79F6C6333
Re: Bug#903438: RFA: asciinema -- Record and share your terminal sessions, the right way
Hello Python Applications Packaging team! I've submitted an RFA for the asciinema package, which is a pure python application, maybe someone from the PAP team wants to carry over. I'll be around to answer questions. Package has no open bugs, latest upstream release has been packaged and uploaded. Packaging is maintained in salsa.debian.org Upstream is helpful, I'd recommend to subscribe to https://github.com/asciinema/asciinema/issues/116 if you plan to maintain the package I no longer use the package, that's why i'm RFAing it Package description: Forget screen recording apps and blurry video. Enjoy a lightweight, purely text based approach to terminal recording. This package provides a command line recorder for asciinema.org service or other instance of asciinema server. thanks! PS: i'm not subscribed to this list, please CC me in answers -- IRC: gfa GPG: 0X44BB1BA79F6C6333
Re: Updating python-jsmin
On Thu, Jan 14, 2016 at 11:16:40AM +, Mattia Rizzolo wrote: > On Thu, Jan 14, 2016 at 02:45:55PM +0800, gustavo panizzo (gfa) wrote: > > On Tue, Jan 12, 2016 at 02:40:46AM +, Mattia Rizzolo wrote: > > > On Tue, Jan 12, 2016 at 10:18:43AM +0800, gustavo panizzo (gfa) wrote: > > > > Hello > > > > > > > > anybody willing to sponsor the upload? > > > > > > > > git.debian.org:/git/collab-maint/python-jsmin.git > > > > > > > > thanks! > > > > > > I can do it, but what should I use as a orig tarball? what I get out of > > > uscan (from pypi) has sha256sum > > > 8e7f19bc2cc467bccd02322dc0a6065d06a038e311f2531af1a33b410afea081 > > > Please consider following a git format with packagin branch > > > > Usually I generate the orig.tar.gz from git tags myself (gbp will do it > > for you) and upload that. > > umh, how gbp does that without pristine-tar? > I don't use gbp to dispatch build, so I wouldn't know how to do that. > Also, if I try: I use this line, it makes everything for me export GIT_PBUILDER_OPTIONS=--twice ; export ARCH=amd64 ;export \ DIST=sid; /usr/bin/time gbp buildpackage --git-builder=git-pbuilder \ --git-cleaner=true -d --git-verbose please note that I use pbuilder to build > > mattia@chase ~/devel/RFS/python-jsmin/python-jsmin (git)-[debian/unstable] % > gbp buildpackage > pyversions: missing X(S)-Python-Version in control file, fall back to > debian/pyversions > pyversions: missing debian/pyversions file, fall back to supported versions > py3versions: no X-Python3-Version in control file, using supported versions > dh clean --buildsystem=python_distutils --with python2,python3 >dh_clean -O--buildsystem=python_distutils > gbp:warning: Pristine-tar branch "pristine-tar" not found > gbp:error: Pristine-tar couldn't checkout "python-jsmin_2.2.0.orig.tar.gz": > pristine-tar: no pristine-tar branch found, use "pristine-tar commit" first > > > Please tell me how I'm supposed to take that tarball, and at this point > also the checksum of what I should expect, since I could start worrying. I've generated a tarball using git archive and push it to pristine-tar branch the md5sum of the tarball is 8f5e2fcdbe62b539efb5686ef0484831 I cloned the repo in a clean sid chroot, built it, and the md5sum coincided thanks! I learned something today :) > > Otherwise (sadly) ignore git and upload the source package somewhere > (mentors.d.n). But I usually prefer git, meh. > > > if the pkg needs a -2 release I base on that, > > if the pkg needs a -2 I use whatever is already on the Debian archive, > ignoring the git repository (but I usually check they matches). > > > I never used pristine-tar > > I have gbp doing all the dirty job for me (i.e. the > `pristine-tar commit` above), I just push it out. > > > I just pushed the changes, could you upload? you will need to force as I > > changed the tag and I merged over the branch from alioth but the end > > result is fine > > moving tags around doesn't need a force. `git pull --tags` will move > them. And thanksfully the HEAD was just moved ahead, not force-pushed > (and you shouldn't need to). > > > > > keybase: http://keybase.io/gfa > > > the key used to sign the tags on that repo is not the same as the one in > > > keybase, btw. doesn't really help. (063A6583 is the one used, 9F6C6333 > > > the one on keybase) > > > -- > 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 `- -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: http://keybase.io/gfa
Re: Updating python-jsmin
Hello anybody willing to sponsor the upload? git.debian.org:/git/collab-maint/python-jsmin.git thanks! On Wed, Dec 23, 2015 at 06:48:03PM +0800, gustavo panizzo (gfa) wrote: > I will update the pkg, last updates weren't difficult so I expect to get it > done soon. > > Pkg is already on git, in collab-maint > > > PS: sorry for the top posting > > On December 23, 2015 6:03:13 PM GMT+08:00, Christopher Baines > <ch...@cbaines.net> wrote: > >On 23/12/15 00:07, gustavo panizzo (gfa) wrote: > >> On Tue, Dec 22, 2015 at 05:44:53PM +, Christopher Baines wrote: > >>> python-jsmin [1] is not currently maintained by the Python Modules > >Team, > >>> but I have made a attempt at updating it to the latest upstream > >version > >>> in a manor compliant with the team policy. > >> > >> do you have a link for the team policy? > > > >Yes, you can find it here: > > https://python-modules.alioth.debian.org/policy.html > > > >> You could have open a bug and I would update the pkg, or just ping > >me. > >> to get it updated to the latest version. > > > >Ok, getting an up to date package in Debian would be great. Are you now > >planning on updating it? > > > >>> You can find the package here [2]. Is anyone (including the current > >>> maintainer CC'ed) interested in updating this package, and possibly > >>> bringing it in to the team? > >> > >> I'm OK moving it into the python modules team, if I don't have to > >change > >> my workflow much, or follow another mailing list > > > >Sounds like team maintenance is not the best option then at the moment, > >as I imagine that there are significant workflow changes (the > >python-jsmin package is not in Git at the moment). > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: http://keybase.io/gfa
Re: Updating python-jsmin
On Thu, Dec 24, 2015 at 05:49:01AM +1100, Ben Finney wrote: > Christopher Baines <ch...@cbaines.net> writes: > > > On 23/12/15 10:48, gustavo panizzo (gfa) wrote: > > > Pkg is already on git, in collab-maint > > > > Ah, sorry, I missed that. I just used apt-get source to get the source > > package. see bellow > > For future reference: The ‘debcheckout(1)’ command will automatically > query the package's “VCS-*” fields and get the source from the specified > VCS repository. good to know that > > That currently fails for ‘python-jsmin’. Gustavo, please read the > Developer's Reference §6.2.5 and add the appropriate “VCS-*” fields to > the source package. yes, that was my bad. I had an updated package in alioth but it never went out to debian archive, that's why Christopher didn't see it. sorry about that. I've pushed to alioth an 2.2.0-1 package, I plan to contact my sponsor to upload to debian on Monday My package is not that far from python modules team policy so maybe in next releases I will move into it thanks everybody! > > -- > \ “We suffer primarily not from our vices or our weaknesses, but | > `\from our illusions.” —Daniel J. Boorstin, historian, 1914–2004 | > _o__) | > Ben Finney <b...@benfinney.id.au> -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: http://keybase.io/gfa
Re: Updating python-jsmin
I will update the pkg, last updates weren't difficult so I expect to get it done soon. Pkg is already on git, in collab-maint PS: sorry for the top posting On December 23, 2015 6:03:13 PM GMT+08:00, Christopher Baines <ch...@cbaines.net> wrote: >On 23/12/15 00:07, gustavo panizzo (gfa) wrote: >> On Tue, Dec 22, 2015 at 05:44:53PM +, Christopher Baines wrote: >>> python-jsmin [1] is not currently maintained by the Python Modules >Team, >>> but I have made a attempt at updating it to the latest upstream >version >>> in a manor compliant with the team policy. >> >> do you have a link for the team policy? > >Yes, you can find it here: > https://python-modules.alioth.debian.org/policy.html > >> You could have open a bug and I would update the pkg, or just ping >me. >> to get it updated to the latest version. > >Ok, getting an up to date package in Debian would be great. Are you now >planning on updating it? > >>> You can find the package here [2]. Is anyone (including the current >>> maintainer CC'ed) interested in updating this package, and possibly >>> bringing it in to the team? >> >> I'm OK moving it into the python modules team, if I don't have to >change >> my workflow much, or follow another mailing list > >Sounds like team maintenance is not the best option then at the moment, >as I imagine that there are significant workflow changes (the >python-jsmin package is not in Git at the moment). -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: Updating python-jsmin
On Tue, Dec 22, 2015 at 05:44:53PM +, Christopher Baines wrote: > python-jsmin [1] is not currently maintained by the Python Modules Team, > but I have made a attempt at updating it to the latest upstream version > in a manor compliant with the team policy. do you have a link for the team policy? You could have open a bug and I would update the pkg, or just ping me. to get it updated to the latest version. > > You can find the package here [2]. Is anyone (including the current > maintainer CC'ed) interested in updating this package, and possibly > bringing it in to the team? I'm OK moving it into the python modules team, if I don't have to change my workflow much, or follow another mailing list > > Thanks, > > Chris cheers! > > 1: https://tracker.debian.org/pkg/python-jsmin > 2: http://git.cbaines.net/python-jsmin/ -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: http://keybase.io/gfa
