Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #12503
| From | Sandro Tosi <morph@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: [Python-modules-team] python-xlib_0.26-1_source.changes ACCEPTED into unstable |
| Date | 2020-04-22 23:50 +0200 |
| Message-ID | <zYvpL-2gq-5@gated-at.bofh.it> (permalink) |
| References | <zYvpL-2gq-7@gated-at.bofh.it> <zYvpM-2gq-9@gated-at.bofh.it> <zYvpM-2gq-11@gated-at.bofh.it> <zYvpM-2gq-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Andrej, can you please clarify why you're keep using pristine-lfs even when prompted not to? this is just from 2 packages uploaded in the last hour (ftr, pyopenssl is broken now..) https://salsa.debian.org/python-team/modules/pyopenssl/-/tree/pristine-lfs https://salsa.debian.org/python-team/modules/urwid/-/tree/pristine-lfs On Sat, Mar 21, 2020 at 3:31 PM Scott Kitterman <debian@kitterman.com> wrote: > > On Saturday, March 21, 2020 3:02:27 PM EDT Andrej Shadura wrote: > > Hi, > > > > On Sat, 21 Mar 2020 at 19:39, Sandro Tosi <morph@debian.org> wrote: > > > > On Sat, 21 Mar 2020 at 18:01, Sandro Tosi <morph@debian.org> wrote: > > > > > Andrej, > > > > > why the pristine-tar information are now in a `pristine-lfs` branch? > > > > > where did the other pristine-tar deltas go? > > > > > > > > Because it’s simpler and better as it guarantees the tarballs are bit > > > > to bit identical, which pristine-tar so often fails to do. There was > > > > no pristine-tar or pristine-lfs information for earlier uploads. > > > > > > but our team policy requires to use pristine-tar: > > > https://salsa.debian.org/python-team/tools/python-modules/blob/master/poli > > > cy.rst > > > > > > please adjust, so that we can all use the same tools and procedures. > > > > I suggest we rather change the policy since at the moment this point > > lacks any rationale and isn’t providing any benefit since the > > pristine-tar data are only useful for minor updates of the package > > (e.g. when the upstream source hasn’t changed) and pristine-tar is > > known to be a huge hack and fail to provide correct tarballs, > > especially when xz is used. > > When you joined the team, you agreed to follow the team policies. Please do > so. > > The way to get the policy changed is not to ignore it and then get aggressive > when called on it. > > Personally, I use the pristine-tar branch routinely (I used it multiple times > just yesterday) and I've never had a problem with it. Personally, while I > know it's a hack, it's a working hack. > > Please do as you've been asked and then we can have a nice conversation about > if we should change the way the team works. > > Scott K > _______________________________________________ > Python-modules-team mailing list > Python-modules-team@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar | Unroll thread
Re: [Python-modules-team] python-xlib_0.26-1_source.changes ACCEPTED into unstable Sandro Tosi <morph@debian.org> - 2020-04-22 23:50 +0200 Re: [Python-modules-team] python-xlib_0.26-1_source.changes ACCEPTED into unstable Andrej Shadura <andrewsh@debian.org> - 2020-04-23 08:30 +0200
csiph-web