Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Thomas Goirand Newsgroups: linux.debian.maint.python Subject: Re: Updating python-jsmin Date: Fri, 15 Jan 2016 04:00:02 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Fri Jan 15 02:56:27 2016 Old-Return-Path: X-Amavis-Spam-Status: No, score=-5.979 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 NOT_IN_BL_NJABL=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .debian. - helo: .mx.atlanta.gplhost. - helo-domain: .gplhost.) FROM/MX_MATCHES_NOT_HELO(DOMAIN)=0; rate: -5 Organization: Debian User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Mailing-List: archive/latest/13418 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/56985FBE.2060405@debian.org Approved: robomod@news.nic.it Lines: 39 Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org X-Original-Date: Fri, 15 Jan 2016 10:55:58 +0800 X-Original-Message-ID: <56985FBE.2060405@debian.org> X-Original-References: <56798C15.7080300@cbaines.net> <20151223000700.GC24201@io.zumbi.casa> <567A7161.1010606@cbaines.net> <80B6E0FF-A3F1-4570-A466-D43025D9B672@zumbi.com.ar> <20160112021843.GD12222@gustavo-nb.RACKSPACE.CORP> <20160112024046.GE25876@chase.mapreri.org> <20160114064555.GJ12222@gustavo-nb.RACKSPACE.CORP> <20160114111640.GA10061@chase.mapreri.org> Xref: csiph.com linux.debian.maint.python:8099 On 01/14/2016 07:16 PM, Mattia Rizzolo wrote: >> Usually I generate the orig.tar.gz from git tags myself (gbp will do i= t >> > for you) and upload that. > umh, how gbp does that without pristine-tar? Just tell gbp to use tags this way: # cat debian/gbp.conf [DEFAULT] debian-branch =3D somethingyoulike upstream-tag =3D %(version)s compression =3D xz It's very convenient. I like it a way more than using pristine tar, which forces you to use 3 branches, when really, a single one is needed. This way, it is also very easy to tag any commit and package that. You can produce the tarball using something like this: DEBPKGNAME=3D`dpkg-parsechangelog -S Source` \ VERSION=3D`dpkg-parsechangelog -S Version | sed -e 's/[-].*//'` \ git archive --prefix=3D$(DEBPKGNAME)-$(VERSION)/ $(GIT_TAG) \ | xz >../$(DEBPKGNAME)_$(VERSION).orig.tar.xz Note that you may want to add this to the VERSION thing to handle EPOCH: -e 's/^[[:digit:]]*://'. And also, since the -S option for dpkg-parsechangelog doesn't work in trusty, you may prefer to use grep / sed / awk. These days, 99,99% of my upstream authors are using a public Git repository. They sometime forget to tag before releasing to PyPi, however, it's trivial to find out which commit matches the PyPi release (most of the time, a quick look at matching release and commit dates are enough to find out). Cheers, Thomas Goirand (zigo)