Bug#962158: lintian: New very problematic --fail-on default value

2020-06-18 Thread Chris Lamb
Chris Lamb wrote: > I'd like to perform another Lintian release but for various reasons > I'd prefer to have this issue addressed before doing another upload. Just to be 100% explicit here, I don't feel I can cut a new release until this bug is resolved. Regards, -- ,''`. : :' :

Bug#962158: lintian: New very problematic --fail-on default value

2020-06-12 Thread Guillem Jover
Control: tags -1 patch *Sigh* On Wed, 2020-06-10 at 08:38:05 -0700, Felix Lechner wrote: > On Tue, Jun 9, 2020 at 11:15 PM Chris Lamb wrote: > > > > Felix, can you help out? I am not in a position to contribute to this > > discussion itself. > > Well, I wish I could. Guillem makes many

Processed: Re: Bug#962158: lintian: New very problematic --fail-on default value

2020-06-12 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #962158 [lintian] lintian: Swapped exit statuses and --fail-on default value require downstream adjustments Added tag(s) patch. -- 962158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962158 Debian Bug Tracking System Contact

Bug#962158: lintian: New very problematic --fail-on default value

2020-06-11 Thread Chris Lamb
Felix Lechner wrote: > It would also give me more time to understand the possibly > unreasonable burden on Lintian users across Debian and the derivative > ecosystem. Simon may receive feedback from Ubuntu, a significant > derivative. If there are real problems, I am happy to discuss a > solution

Bug#962158: lintian: New very problematic --fail-on default value

2020-06-10 Thread Felix Lechner
Hi Chris, On Tue, Jun 9, 2020 at 11:15 PM Chris Lamb wrote: > > Felix, can you help out? I am not in a position to contribute to this > discussion itself. Well, I wish I could. Guillem makes many alarmist statements, but fails to explain why the change is an undue burden. I also do not know how

Bug#962158: lintian: New very problematic --fail-on default value

2020-06-10 Thread Chris Lamb
Guillem Jover wrote: > [..] I'd like to perform another Lintian release but for various reasons I'd prefer to have this issue addressed before doing another upload. I already regret that this migrated to bullseye before we elevated the severity. Felix, can you help out? I am not in a position

Bug#962158: lintian: New very problematic --fail-on default value

2020-06-04 Thread Guillem Jover
On Thu, 2020-06-04 at 15:58:47 -0700, Felix Lechner wrote: > > This change means that any current caller which uses lintian as part > > of its acceptance testing will now silently let broken things through > > As I explained on IRC this statement is probably untrue (and you did > not have the

Bug#962158: lintian: New very problematic --fail-on default value

2020-06-04 Thread Guillem Jover
Hi! On Thu, 2020-06-04 at 23:06:29 +0100, Chris Lamb wrote: > severity 962158 serious > thanks > > Severity: important > > > > This probably deserves to be serious, but I'm not sure I can be > > bothered… > > I can relate to this feeling so let me do this for you. At the very > least, this

Bug#962158: lintian: New very problematic --fail-on default value

2020-06-04 Thread Chris Lamb
severity 962158 serious thanks Guillem, > Severity: important > > This probably deserves to be serious, but I'm not sure I can be > bothered… I can relate to this feeling so let me do this for you. At the very least, this change now won't hit bullseye before being resolved. Regards, --

Processed: Re: Bug#962158: lintian: New very problematic --fail-on default value

2020-06-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 962158 serious Bug #962158 [lintian] lintian: Swapped exit statuses and --fail-on default value require downstream adjustments Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need