Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #9708
| From | Jeremy Stanley <fungi@yuggoth.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: a few quick questions on gbp pq workflow |
| Date | 2017-08-06 21:00 +0200 |
| Message-ID | <ubyWl-5Tz-17@gated-at.bofh.it> (permalink) |
| References | <ubvc6-3xe-7@gated-at.bofh.it> <ubwhP-4rV-7@gated-at.bofh.it> <ubwBc-4yy-21@gated-at.bofh.it> <ubytk-5JT-25@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
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 it's possible (have tests, don't have prebuilds, ...) > - use git tag tarballs (https://github.com/<group>/<projects>/tags) > > I already migrated few packages OS->DPMT so far. 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 are built from DFSG-compliant upstream source, included in the archive for that matter, then leaving the tarball pristine shouldn't be a policy violation, right? That's like repacking a tarball for an autotools-using project because upstream is shipping a configure script built from an included configure.in file. Pretty sure OpenStack at least would consider any content which requires Debian package maintainers to alter tarballs prior to including them in the archive as fairly serious bug in its software. -- Jeremy Stanley
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
a few quick questions on gbp pq workflow Allison Randal <allison@lohutok.net> - 2017-08-06 17:00 +0200
Re: a few quick questions on gbp pq workflow Jeremy Stanley <fungi@yuggoth.org> - 2017-08-06 18:10 +0200
Re: a few quick questions on gbp pq workflow Scott Kitterman <debian@kitterman.com> - 2017-08-06 18:30 +0200
Re: a few quick questions on gbp pq workflow Ondrej Novy <novy@ondrej.org> - 2017-08-06 20:30 +0200
Re: a few quick questions on gbp pq workflow Jeremy Stanley <fungi@yuggoth.org> - 2017-08-06 21:00 +0200
Re: a few quick questions on gbp pq workflow Ghislain Vaillant <ghisvail@gmail.com> - 2017-08-06 21:10 +0200
Re: a few quick questions on gbp pq workflow Jeremy Stanley <fungi@yuggoth.org> - 2017-08-06 21:20 +0200
Re: a few quick questions on gbp pq workflow Thomas Goirand <zigo@debian.org> - 2017-09-04 00:00 +0200
Re: a few quick questions on gbp pq workflow Ondrej Novy <novy@ondrej.org> - 2017-08-06 23:50 +0200
Re: a few quick questions on gbp pq workflow Jeremy Stanley <fungi@yuggoth.org> - 2017-08-07 00:30 +0200
Re: a few quick questions on gbp pq workflow Thomas Goirand <zigo@debian.org> - 2017-09-04 00:20 +0200
Re: a few quick questions on gbp pq workflow Scott Kitterman <debian@kitterman.com> - 2017-08-07 05:00 +0200
Re: a few quick questions on gbp pq workflow Paul Wise <pabs@debian.org> - 2017-08-07 16:50 +0200
Re: a few quick questions on gbp pq workflow Diane Trout <diane@ghic.org> - 2017-08-08 00:20 +0200
Re: a few quick questions on gbp pq workflow Scott Kitterman <debian@kitterman.com> - 2017-08-08 01:20 +0200
Re: a few quick questions on gbp pq workflow Scott Kitterman <debian@kitterman.com> - 2017-08-06 21:00 +0200
Re: a few quick questions on gbp pq workflow Ghislain Vaillant <ghisvail@gmail.com> - 2017-08-06 21:10 +0200
Re: a few quick questions on gbp pq workflow Barry Warsaw <barry@debian.org> - 2017-08-07 20:00 +0200
Re: a few quick questions on gbp pq workflow Thomas Goirand <zigo@debian.org> - 2017-09-04 00:00 +0200
Re: a few quick questions on gbp pq workflow Brian May <bam@debian.org> - 2017-08-07 01:10 +0200
csiph-web