Re: a few quick questions on gbp pq workflow

2017-08-06 Thread Ondrej Novy
Hi, 2017-08-06 12:26 GMT-04:00 Scott Kitterman : > > I don't work on the OpenStack packages, but I do maintain a reasonable > number of Python packages. I always work from the released tarball. I > haven't added the keys yet to verify all my packages, but am gradually >

Re: a few quick questions on gbp pq workflow

2017-08-06 Thread Ghislain Vaillant
On 06/08/17 19:53, Jeremy Stanley wrote: Why would you need to repack a tarball just because it contains prebuilt docs (non-DFSG-free licensed documentation aside)? I'm all for rebuilding those at deb build time just to be sure you have the right deps packaged too, but if the ones in the tarball

Re: a few quick questions on gbp pq workflow

2017-08-06 Thread Jeremy Stanley
On 2017-08-06 20:00:59 +0100 (+0100), Ghislain Vaillant wrote: [...] > You'd still have to clean the pre-built files, since they would be > overwritten by the build system and therefore dpkg-buildpackage > would complain if you run the build twice. > > So, you might as well just exclude them from

Re: a few quick questions on gbp pq workflow

2017-08-06 Thread Ghislain Vaillant
On 06/08/17 19:56, Scott Kitterman wrote: Generally when I find shortcomings in the tarball, I file bugs upstream. In general, I've found upstream developers to be accepting of such changes. Same here. There's no need to DFSG the tarball if you can rebuild the docs. The best way to

a few quick questions on gbp pq workflow

2017-08-06 Thread Allison Randal
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. (We'll keep maintaining them, just within DPMT using the DPMT workflow.) After chatting with tumbleweed, the current suggestion is that we should

Re: a few quick questions on gbp pq workflow

2017-08-06 Thread Jeremy Stanley
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. (We'll keep maintaining them, just within > DPMT using the DPMT workflow.) > >

Re: a few quick questions on gbp pq workflow

2017-08-06 Thread Scott Kitterman
On August 6, 2017 2:11:13 PM EDT, Ondrej Novy wrote: >Hi, > >2017-08-06 12:26 GMT-04:00 Scott Kitterman : >> >> I don't work on the OpenStack packages, but I do maintain a >reasonable >> number of Python packages. I always work from the released tarball.

Re: a few quick questions on gbp pq workflow

2017-08-06 Thread Scott Kitterman
On August 6, 2017 11:37:51 AM EDT, Jeremy Stanley wrote: >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

Re: a few quick questions on gbp pq workflow

2017-08-06 Thread Jeremy Stanley
On 2017-08-06 14:11:13 -0400 (-0400), Ondrej Novy wrote: > It's not always possible/simple/nice to use sdist, because it contains > prebuild docs. And I don't like to do +dfsg rebuild just for removing docs. > Sometimes sdists doesn't contain tests. > > So my preference is: > >- use sdist if

Re: MBF for deprecating Python2 usage

2017-08-06 Thread Adrian Bunk
On Thu, Aug 03, 2017 at 05:57:01PM -0400, Matthias Klose wrote: > While at DebCamp, Stefano Rivera and I sat down to analyze what needs to be > done > to deprecate Python2 usage within the distribution. It might not be possible > to > drop Python2 for the next release, but there are still too

Re: MBF for deprecating Python2 usage

2017-08-06 Thread Adrian Bunk
On Thu, Aug 03, 2017 at 05:57:01PM -0400, Matthias Klose wrote: > While at DebCamp, Stefano Rivera and I sat down to analyze what needs to be > done > to deprecate Python2 usage within the distribution. It might not be possible > to > drop Python2 for the next release, but there are still too

Re: a few quick questions on gbp pq workflow

2017-08-06 Thread Ondrej Novy
Hi, 2017-08-06 14:53 GMT-04:00 Jeremy Stanley : > Why would you need to repack a tarball just because it contains > prebuilt docs (non-DFSG-free licensed documentation aside)? I'm all > Lintian considers this as "bug": https://lintian.debian.

Re: a few quick questions on gbp pq workflow

2017-08-06 Thread Brian May
Allison Randal writes: > - Will DPMT be following DEP-14 and using the branch name debian/master > instead of master? I believe so. Although from memory the conversion instructions are incomplete on how to change the default branch to debian/master, which is required before

Re: MBF for deprecating Python2 usage

2017-08-06 Thread Christian Seiler
Hi Matthias, On 08/03/2017 11:57 PM, Matthias Klose wrote: > It might not be possible to drop Python2 for the next release, Even if all Python-related packages in Debian were compatible with Python3, I don't think it's a good idea to drop Python2 support in Buster, there are still far too many

Re: a few quick questions on gbp pq workflow

2017-08-06 Thread Scott Kitterman
On August 6, 2017 5:24:59 PM EDT, Ondrej Novy wrote: >Hi, > >2017-08-06 14:53 GMT-04:00 Jeremy Stanley : > >> Why would you need to repack a tarball just because it contains >> prebuilt docs (non-DFSG-free licensed documentation aside)? I'm all >> > >Lintian