Path: csiph.com!news.freedyn.net!aioe.org!bofh.it!news.nic.it!robomod From: Barry Warsaw Newsgroups: linux.debian.maint.python Subject: Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Date: Tue, 16 Aug 2016 00:00:01 +0200 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Aug 15 21:55:49 2016 Old-Return-Path: X-Amavis-Spam-Status: No, score=-10.859 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, LDO_WHITELIST=-5, MISSING_HEADERS=1.021, MURPHY_DRUGS_REL8=0.02, PGPSIGNATURE=-5] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5 X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.30; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/m7rgPmpf.KUNDol+fgV2jVM"; protocol="application/pgp-signature" X-Mailing-List: archive/latest/14116 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20160815175531.2d67c0ab@subdivisions.wooz.org Approved: robomod@news.nic.it Lines: 69 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org X-Original-Date: Mon, 15 Aug 2016 17:55:31 -0400 X-Original-Message-ID: <20160815175531.2d67c0ab@subdivisions.wooz.org> 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:8775 --Sig_/m7rgPmpf.KUNDol+fgV2jVM Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Aug 15, 2016, at 11:44 PM, Thomas Goirand wrote: >If we decide to use gbp-pq, in fact, we're deciding to not decide, and any= one >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). That sounds perfect then! >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). So at a minimum: ----gbp.conf---- [import-orig] pristine-tar =3D True ----gbp.conf---- Looking at my ~/.gbp.conf file, I have a bunch of other entries, some of wh= ich are probably not appropriate for team settings. I'd suggest `sign-tags=3DT= rue` though. *Maybe* also these as conveniences: [import-orig] postimport =3D gbp dch -N%(version)s import-msg =3D New upstream release. What else? Cheers, -Barry --Sig_/m7rgPmpf.KUNDol+fgV2jVM Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXsjpTAAoJEBJutWOnSwa/c04P/3DFtKFB3agq2U74U7FvcOn9 APxE6lYYg63vvXorHW0FMHKpiyKDl5dthCCfPaDUJvHSrJ+rf1NzvSF1j3WvbUem mvgInWm8gpTZJnnWGeHsGf8VKncqTOZRSkX8IWT1T7FB7p0EZ/Nywt+hkWcXKOgh yK4662581LYG3YueuMYbGgIdQQtPzrvVFJ6IQK5251RWRmdbxprDWZximiQ75YG6 cPG9/OzTkBp1htTwLd9TLsrGP2bn8uIJypxN0tCMAjkHCZGOT9DBC40bjyPYcQLO tR/8G8wkl39UTfosrKCwaLTya4D17pExxSpTQG1EcKqxw2z6lShyvSZp5MngaBk0 hJf5ikx5o47QxHG+04tCny1Ry7uBiXAm1G6SGwux5RKqeyynJcaBfCtfhp5NiDGJ t9pC8Ayw7cSK68daQn5R4TV6/YLwiK9Sf+GOYmrblhyADINIR6MTPouCfwnM/D/4 ru4v9E6HqukBBI1ITEPvEN6tubV9VMjV7ToIbMCqy4oOguTw/ZF6OZL4CV5t1Xa7 fIMtTWNNkCp5mXPurYQxbyFfu8ewgojmaSPuukwdWArUKrNex/wvEHzKNR+hZ6EL g4Pew6DynAsQlOEfIs+PUe1j+rC8ooG+3A3SxHZamHEaiWYeCGp7cVO/z167Wzrl ZTmHA4j2f5Xx7EIVLxOq =dGMR -----END PGP SIGNATURE----- --Sig_/m7rgPmpf.KUNDol+fgV2jVM--