Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #8774
| From | Thomas Goirand <zigo@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: using git-dpm or plain git-buildpackage in PAPT and DPMT |
| Date | 2016-08-15 23:50 +0200 |
| Message-ID | <s6xVD-2Er-5@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <s4oab-5fc-11@gated-at.bofh.it> <s4w7D-24x-1@gated-at.bofh.it> <s4wU1-2Bz-23@gated-at.bofh.it> <s4GTp-n4-83@gated-at.bofh.it> <s4IBQ-1DK-11@gated-at.bofh.it> |
| Organization | Debian |
On 08/10/2016 10:41 PM, Barry Warsaw wrote: > * IOW, if > you choose to use gbp-pq, am I forced to do so when I modify the same repo? > Or if you choose to use PoQ (plain 'ol quilt), will that affect how others > can co-maintain the package in git? That's the point. If we decide to use gbp-pq, in fact, we're deciding to not decide, and anyone can use PoQ (my choice, for example). Indeed, the way to store the patches is PoQ, and you then "gbp-pq import", modify, then "gbp-pq export" and store the packaging branch like this (ie: like a PoQ branch). So, basically, we'll be back to what everyone else is doing (ie: 99% of git maintained packages in Debian as much as I saw). On 08/11/2016 01:12 AM, Simon McVittie wrote: > no other special metadata present in git (you can optionally commit a > debian/gbp.conf, and I would recommend it, but it isn't required) IMO, that's required if we decide to continue using pristine-tar (which I don't think is a good idea, but let's not discuss that, as there seem to be a consensus for it). On 08/11/2016 01:12 AM, Simon McVittie wrote: > Not good for gbp-pq (it works OK, but an import/export round-trip will > mangle the metadata if you don't take steps to preserve it): > > Author: Donald Duck <donald@example.com> > Description: Reticulate splines correctly > This regressed in 2.0. > . > In particular, this broke embiggening. > Last-update: Fri, 01 Apr 2016 12:34:00 +0100 > Origin: vendor, Debian > Forwarded: http://bugs.example.org/123 > --- > [diff goes here] > > Regards, > S If this is what gbp pq does, then that's the *right* thing (I don't remember, probably because it didn't destroy my Debian headers, which I carefully crafted by hand...). Cheers, Thomas
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
pypi2deb 1.20160809 and --profile dpmt Piotr Ożarowski <piotr@debian.org> - 2016-08-09 21:30 +0200
Re: pypi2deb 1.20160809 and --profile dpmt Daniel Stender <stender@debian.org> - 2016-08-10 00:00 +0200
Re: pypi2deb 1.20160809 and --profile dpmt Barry Warsaw <barry@debian.org> - 2016-08-10 00:10 +0200
PAPT Git (was: pypi2deb 1.20160809 and --profile dpmt) "W. Martin Borgert" <debacle@debian.org> - 2016-08-10 01:00 +0200
Re: PAPT Git (was: pypi2deb 1.20160809 and --profile dpmt) Sandro Tosi <morph@debian.org> - 2016-08-10 09:30 +0200
Re: PAPT Git Piotr Ożarowski <piotr@debian.org> - 2016-08-10 09:40 +0200
Re: using git-dpm or plain git-buildpackage in PAPT and DPMT (was: PAPT Git) Thomas Goirand <zigo@debian.org> - 2016-08-10 10:20 +0200
Re: using git-dpm or plain git-buildpackage in PAPT and DPMT (was: PAPT Git) "W. Martin Borgert" <debacle@debian.org> - 2016-08-10 11:00 +0200
Re: using git-dpm or plain git-buildpackage in PAPT and DPMT (was: PAPT Git) Brian May <bam@debian.org> - 2016-08-10 12:50 +0200
Re: using git-dpm or plain git-buildpackage in PAPT and DPMT (was: PAPT Git) Barry Warsaw <barry@debian.org> - 2016-08-10 16:20 +0200
Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Nikolaus Rath <Nikolaus@rath.org> - 2016-08-10 21:00 +0200
Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Barry Warsaw <barry@debian.org> - 2016-08-10 22:50 +0200
Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Simon McVittie <smcv@debian.org> - 2016-08-11 01:20 +0200
Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Barry Warsaw <barry@debian.org> - 2016-08-11 15:30 +0200
Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Simon McVittie <smcv@debian.org> - 2016-08-11 18:10 +0200
Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Thomas Goirand <zigo@debian.org> - 2016-08-15 23:50 +0200
Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Barry Warsaw <barry@debian.org> - 2016-08-16 00:00 +0200
Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Raphael Hertzog <hertzog@debian.org> - 2016-08-10 23:00 +0200
Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Brian May <bam@debian.org> - 2016-08-12 12:40 +0200
Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Sergio Durigan Junior <sergiodj@sergiodj.net> - 2016-08-13 00:00 +0200
Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Barry Warsaw <barry@debian.org> - 2016-08-13 00:40 +0200
Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Sergio Durigan Junior <sergiodj@sergiodj.net> - 2016-08-16 22:40 +0200
Re: using git-dpm or plain git-buildpackage in PAPT and DPMT IOhannes m zmölnig (Debian/GNU) <umlaeute@debian.org> - 2016-08-31 23:50 +0200
Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Barry Warsaw <barry@debian.org> - 2016-09-02 21:20 +0200
Re: pypi2deb 1.20160809 and --profile dpmt IOhannes m zmölnig (Debian/GNU) <umlaeute@debian.org> - 2016-08-31 23:50 +0200
csiph-web