Re: NEW processing friction

2022-02-07 Thread Scott Kitterman
On February 8, 2022 2:38:48 AM UTC, Holger Levsen wrote: >On Mon, Feb 07, 2022 at 09:28:16PM -0500, Theodore Ts'o wrote: >> The argument why a package which has an upstream-induced shared >> library version bump, has to go through the entire NEW gauntlet [...] > >I hear your frustration but don

Re: NEW processing friction

2022-02-07 Thread Holger Levsen
On Mon, Feb 07, 2022 at 09:28:16PM -0500, Theodore Ts'o wrote: > The argument why a package which has an upstream-induced shared > library version bump, has to go through the entire NEW gauntlet [...] I hear your frustration but don't you think that language like "gauntlet" makes it, uhm, very har

Re: NEW processing friction

2022-02-07 Thread Theodore Ts'o
On Mon, Feb 07, 2022 at 07:05:59PM -0700, Sean Whitton wrote: > Hello, > > On Mon 07 Feb 2022 at 12:00PM -05, Theodore Ts'o wrote: > > > On Mon, Feb 07, 2022 at 12:06:24AM -0700, Sean Whitton wrote: > >> > >> When we treat any of the above just like other RC bugs, we are accepting > >> a lower li

Re: NEW processing friction

2022-02-07 Thread Sean Whitton
Hello, On Mon 07 Feb 2022 at 12:00PM -05, Theodore Ts'o wrote: > On Mon, Feb 07, 2022 at 12:06:24AM -0700, Sean Whitton wrote: >> >> When we treat any of the above just like other RC bugs, we are accepting >> a lower likelihood that the bugs will be found, and also that they will >> be fixed

Re: NEW processing friction

2022-02-07 Thread Scott Kitterman
On February 7, 2022 6:00:16 PM UTC, John Goerzen wrote: > >On Mon, Feb 07 2022, Theodore Ts'o wrote: > >> If we can't do anything else, I suspect we can reduce project a >> friction a lot of we only subject packages to copyright hazing when it >> is a NEW source package, and not when there is a

Re: NEW processing friction

2022-02-07 Thread John Goerzen
On Mon, Feb 07 2022, Theodore Ts'o wrote: > If we can't do anything else, I suspect we can reduce project a > friction a lot of we only subject packages to copyright hazing when it > is a NEW source package, and not when there is a NEW binary package > caused by some usptream maintainers not bei

Bug#1005131: ITP: utf8-locale -- detect a UTF-8-capable locale for running child processes in

2022-02-07 Thread Peter Pentchev
Package: wnpp Severity: wishlist Owner: Peter Pentchev X-Debbugs-Cc: debian-devel@lists.debian.org, r...@debian.org * Package name: utf8-locale Version : 0.2.0 Upstream Author : Peter Pentchev * URL : https://gitlab.com/ppentchev/utf8-locale * License : BSD-2

Re: NEW processing friction

2022-02-07 Thread Theodore Ts'o
On Mon, Feb 07, 2022 at 12:06:24AM -0700, Sean Whitton wrote: > > When we treat any of the above just like other RC bugs, we are accepting > a lower likelihood that the bugs will be found, and also that they will > be fixed Another part of this discussion which shouldn't be lost is the probab

Bug#1005114: ITP: python-model-bakery -- smart object creation facility for Django (Python 3 version)

2022-02-07 Thread Neil Williams
Package: wnpp Severity: wishlist Owner: Neil Williams X-Debbugs-Cc: debian-devel@lists.debian.org, codeh...@debian.org * Package name: python-model-bakery Version : 1.4.0 Upstream Author : berinfontes * URL : https://github.com/model-bakers/model_bakery * License

Re: Salsa CI introducing world-writable permissions

2022-02-07 Thread Andrej Shadura
Hi, On Sun, 6 Feb 2022, at 15:22, John Goerzen wrote: > In the relevant repo, I could type: > > ``` > $ git ls-tree 91df28f0cc4b0d58cfda57fc1cc5c350bdbaf76d -- service/ > 100644 blob ec429c0bbdb50da81ba0fbef5fc516fc5dc5791f > service/nncp-caller.service > 100644 blob af287bb8255a1fbb774777d56b17