On Thu, Jan 14, 2016 at 02:45:55PM +0800, gustavo panizzo (gfa) wrote: > On Tue, Jan 12, 2016 at 02:40:46AM +0000, 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: 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. 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 `-
signature.asc
Description: PGP signature
