Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #8099
| From | Thomas Goirand <zigo@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Updating python-jsmin |
| Date | 2016-01-15 04:00 +0100 |
| Message-ID | <qR2Mi-85x-11@gated-at.bofh.it> (permalink) |
| References | (3 earlier) <qIP9w-8u4-33@gated-at.bofh.it> <qPWIV-2PA-5@gated-at.bofh.it> <qPXbX-30c-7@gated-at.bofh.it> <qQJTk-3cp-9@gated-at.bofh.it> <qQO6C-6bn-21@gated-at.bofh.it> |
| Organization | Debian |
On 01/14/2016 07:16 PM, Mattia Rizzolo wrote: >> 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? Just tell gbp to use tags this way: # cat debian/gbp.conf [DEFAULT] debian-branch = somethingyoulike upstream-tag = %(version)s compression = 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=`dpkg-parsechangelog -S Source` \ VERSION=`dpkg-parsechangelog -S Version | sed -e 's/[-].*//'` \ git archive --prefix=$(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)
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Updating python-jsmin Christopher Baines <chris@cbaines.net> - 2015-12-22 18:50 +0100
Re: Updating python-jsmin "gustavo panizzo (gfa)" <gfa@zumbi.com.ar> - 2015-12-23 01:20 +0100
Re: Updating python-jsmin Christopher Baines <chris@cbaines.net> - 2015-12-23 11:10 +0100
Re: Updating python-jsmin "gustavo panizzo (gfa)" <gfa@zumbi.com.ar> - 2015-12-23 11:50 +0100
Re: Updating python-jsmin Christopher Baines <chris@cbaines.net> - 2015-12-23 12:40 +0100
Re: Updating python-jsmin Ben Finney <ben+debian@benfinney.id.au> - 2015-12-23 20:10 +0100
Re: Updating python-jsmin "gustavo panizzo (gfa)" <gfa@zumbi.com.ar> - 2015-12-25 18:20 +0100
Re: Updating python-jsmin "gustavo panizzo (gfa)" <gfa@zumbi.com.ar> - 2016-01-12 03:20 +0100
Re: Updating python-jsmin Mattia Rizzolo <mattia@debian.org> - 2016-01-12 03:50 +0100
Re: Updating python-jsmin "gustavo panizzo (gfa)" <gfa@zumbi.com.ar> - 2016-01-14 07:50 +0100
Re: Updating python-jsmin Mattia Rizzolo <mattia@debian.org> - 2016-01-14 12:20 +0100
Re: Updating python-jsmin "gustavo panizzo (gfa)" <gfa@zumbi.com.ar> - 2016-01-14 16:50 +0100
Re: Updating python-jsmin Mattia Rizzolo <mattia@debian.org> - 2016-01-14 17:30 +0100
Re: Updating python-jsmin Thomas Goirand <zigo@debian.org> - 2016-01-15 04:00 +0100
Re: Updating python-jsmin Dmitry Shachnev <mitya57@debian.org> - 2016-01-14 16:50 +0100
Re: Updating python-jsmin Barry Warsaw <barry@debian.org> - 2016-01-14 17:50 +0100
csiph-web