Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Thomas Goirand Newsgroups: linux.debian.maint.python Subject: Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Date: Mon, 15 Aug 2016 23:50:01 +0200 Message-ID: References: X-Original-To: Barry Warsaw , debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Aug 15 21:45:29 2016 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.88 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5 X-Enigmail-Draft-Status: N1110 Organization: Debian User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.1.0 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Mailing-List: archive/latest/14115 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/bfd96239-9434-e967-bc97-f0cae888ee5f@debian.org Approved: robomod@news.nic.it Lines: 48 Sender: robomod@news.nic.it X-Original-Date: Mon, 15 Aug 2016 23:44:53 +0200 X-Original-Message-ID: X-Original-References: <20160809192733.pfsnzejxlmd3knbe@p1otr.com> <356e3407-7970-5c4f-f963-60664898548a@debian.org> <20160809225020.GA30494@fama> <87fuqccv6p.fsf@thinkpad.rath.org> <20160810164140.48f7fd42@subdivisions.wooz.org> Xref: csiph.com linux.debian.maint.python:8774 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 o= thers > 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 > 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