Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Barry Warsaw Newsgroups: linux.debian.maint.python Subject: Re: [Python-modules-team] partd_0.3.8-1_source.changes ACCEPTED into unstable Date: Fri, 02 Jun 2017 17:40:01 +0200 Message-ID: References: X-Original-To: X-Mailbox-Line: From debian-python-request@lists.debian.org Fri Jun 2 15:36:10 2017 Old-Return-Path: X-Amavis-Spam-Status: No, score=-10.76 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, PGPSIGNATURE=-5, SARE_LWSHORTT=1.24] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5 Organization: The Organization of Unorganized Woozalists X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/=2ZUiV422vb0nxcOKFLjF8c"; protocol="application/pgp-signature" X-Mailing-List: archive/latest/14927 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20170602113552.4dffe63f@subdivisions.wooz.org Approved: robomod@news.nic.it Lines: 61 Sender: robomod@news.nic.it X-Original-Date: Fri, 2 Jun 2017 11:35:52 -0400 X-Original-Message-ID: <20170602113552.4dffe63f@subdivisions.wooz.org> X-Original-References: Xref: csiph.com linux.debian.maint.python:9550 --Sig_/=2ZUiV422vb0nxcOKFLjF8c Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi Diane, On Jun 02, 2017, at 05:48 AM, Debian FTP Masters wrote: > partd (0.3.8-1) unstable; urgency=3Dmedium > . > * Switch from git-dpm to gbp I may be misremembering our previous discussions on the topic, but we all k= now that in the long term we want to convert off of git-dpm. My recollection was that in the short term, "officially" we want to opportunistically convert packages as an experiment, and to work out the st= eps needed, so that at some time in the future, we'd mass migrate the bulk of o= ur packages. I'm curious, did you follow the steps outlined in https://wiki.debian.org/Python/GitPackagingPQ to do the conversion? (Search for "Converting git-dpm to gbp pq") or did you follow some other process? = Are you adopting gbp-pq for your own workflow? Do you have any insights that w= ill help others convert, or that can guide our future mass migration? Is there anything you can add to the wiki page to help others when they opportunistically convert? For the team: should we just allow opportunistic conversions and live with a mixed git-dpm/gbp state in our packages for a while? Cheers, -Barry --Sig_/=2ZUiV422vb0nxcOKFLjF8c Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJZMYXYAAoJEBJutWOnSwa/dEkP/3PpsyRk+bVd+k111uWJCx+j iZyOiZUibN6fdH6IytiFS3fbliwFMQKYjRks86vkEZR2bncICGs8uoBG2BIMbEoK NWHLAemyilkWC+MVjJL8xk67B9X4ksuRey0dIh4g3qyKDeehV8roWr/O5SKMA2EB dqYg1S2GH5feSDx8SCbQTye9JMfWFx/JK7c4Vkp7//fH/8Uex9og1zUD5T1PM7cM 6BLwGRyBJvrRRmYiKJp464typjomezGbZCVIeyPuw9l8hr1TBie8Q3uiSWno22Ln g4IvlaUk8Kh3JsGEtsxVEtEuu++h+NR6iN5mIAy4yArEXuxgoH4i8Ij7tmJtZi+p kaiKQKbUa7Wr7Ht3epWewyQz3ztiG4MJzwwgqMiTRcePoG4o0lEUXVwXDna87rf4 ns4+JRdiSS3CK2WUb7psvBw9bCKoN72MlSpWTQE1dQymbMSU5S4O4PecmHzj8X/O dPcoZm2O9epaydJwkkqrBNsh07Oz96EJc7d2dYP6zJb+D0wF0cYo8fJw3tD8cArf j6L5Ho45uxShAvY3szOUqeskDt5JuinMUet7a76vL8eHp2Feg0C5g1afxMhDIuvG DTtCp896c8hH+DF3FgDTQGiWcTwVJGSLn93anChs5mI64pDUvVAgKBlvzPRSPqTB Pqb7mkjzo8dzthLsP+ig =+cbM -----END PGP SIGNATURE----- --Sig_/=2ZUiV422vb0nxcOKFLjF8c--