Path: csiph.com!news.mixmin.net!news.unit0.net!news.panservice.it!bofh.it!news.nic.it!robomod
From: Scott Kitterman <debian@kitterman.com>
Newsgroups: linux.debian.maint.python
Subject: Re: a few quick questions on gbp pq workflow
Date: Sun, 06 Aug 2017 18:30:02 +0200
Message-ID: <ubwBc-4yy-21@gated-at.bofh.it>
References: <ubvc6-3xe-7@gated-at.bofh.it> <ubwhP-4rV-7@gated-at.bofh.it>
Old-Return-Path: <debian@kitterman.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Approved: robomod@news.nic.it
Lines: 39
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:9706



On August 6, 2017 11:37:51 AM EDT, Jeremy Stanley <fungi@yuggoth=2Eorg> wr=
ote:
>On 2017-08-06 10:44:36 -0400 (-0400), Allison Randal wrote:
>> The OpenStack packaging team has been sprinting at DebCamp, and
>> we're finally ready to move all general Python dependencies for
>> OpenStack over to DPMT=2E (We'll keep maintaining them, just within
>> DPMT using the DPMT workflow=2E)
>>=20
>> After chatting with tumbleweed, the current suggestion is that we
>> should migrate the packages straight into gbp pq instead of making
>> an intermediate stop with git-dpm=2E
>[=2E=2E=2E]
>
>More a personal curiosity on my part (I'm now a little disappointed
>that I didn't make time to attend), but are you planning to leverage
>pristine tarballs as part of this workflow shift so you can take
>advantage of the version details set in the sdist metadata and the
>detached OpenPGP signatures provided upstream? Or are you sticking
>with operating on a local fork of upstream Git repositories (and
>generating intermediate sdists on the fly or supplying version data
>directly from the environment via debian/rules)?
>
>I'm eager to see what upstream release management features you're
>taking advantage of so we can better know which of those efforts are
>valuable to distro package maintainers=2E

I don't work on the OpenStack packages, but I do maintain a reasonable num=
ber of Python packages=2E  I always work from the released tarball=2E  I ha=
ven't added the keys yet to verify all my packages, but am gradually doing =
so as I have time=2E

I know some people like working from the upstream git (and the team mainte=
nance workflow allows for either), but I definitely prefer working from the=
 upstream tarballs and appreciate the effort that goes into producing them=
=2E

Scott K