Thijs wrote:
>On Saturday 5 January 2008 14:43, Steve McIntyre wrote:
>> As you might expect (as I was the requester for this feature) I'd
>> *really* prefer the former option. My initial reasoning for it is that
>> I want to make it immediately visible to sponsors if a package has
>> suppressed li
On Saturday 5 January 2008 14:43, Steve McIntyre wrote:
> As you might expect (as I was the requester for this feature) I'd
> *really* prefer the former option. My initial reasoning for it is that
> I want to make it immediately visible to sponsors if a package has
> suppressed lintian warnings. If
Raphael Hertzog <[EMAIL PROTECTED]> writes:
> On Sat, 05 Jan 2008, Lars Wirzenius wrote:
>> This might be too much DWIM, but... supposed lintian would, by default,
>> report the number of suppressed warnings, but only if the person
>> running it is not the maintainer? Lintian could use the same lo
On Sat, 05 Jan 2008, Lars Wirzenius wrote:
> On la, 2008-01-05 at 13:43 +, Steve McIntyre wrote:
> > As you might expect (as I was the requester for this feature) I'd
> > *really* prefer the former option. My initial reasoning for it is that
> > I want to make it immediately visible to sponsors
On la, 2008-01-05 at 13:43 +, Steve McIntyre wrote:
> As you might expect (as I was the requester for this feature) I'd
> *really* prefer the former option. My initial reasoning for it is that
> I want to make it immediately visible to sponsors if a package has
> suppressed lintian warnings. If
Russ wrote:
>
>* Show the N: line with a count of overrides per package by default and
> provide an option to suppress this output if someone wants.
>
>* Don't show the N: line by default and provide an option to turn it on.
>
>Which should we do?
As you might expect (as I was the requester for t
On 11253 March 1977, Russ Allbery wrote:
> I'd really like to not have to make this decision myself. I'd like to get
> opinions and see if a consensus emerges. I personally always run lintian
> with -iI --show-overrides, so I'm clearly not the target audience for this
> feature one way or the ot
On Thu, 2008-01-03 at 18:28 +0100, Christian Perrier wrote:
> Quoting Russ Allbery ([EMAIL PROTECTED]):
>
> > * Show the N: line with a count of overrides per package by default and
> > provide an option to suppress this output if someone wants.
> >
> > * Don't show the N: line by default and p
Hi,
On Thu, 2008-01-03 at 08:55:06 +0100, Raphael Hertzog wrote:
> On Wed, 02 Jan 2008, Russ Allbery wrote:
> > > Currently on dpkg I have 4 N: lines: one per deb + one for the
> > > .dsc. That clutters the output a bit too much to my taste. And ideally
> > > it should be at the end of the output
Quoting Russ Allbery ([EMAIL PROTECTED]):
> * Show the N: line with a count of overrides per package by default and
> provide an option to suppress this output if someone wants.
>
> * Don't show the N: line by default and provide an option to turn it on.
My first reaction would have been supp
Steve Langasek <[EMAIL PROTECTED]> writes:
> On Thu, Jan 03, 2008 at 12:21:54AM -0800, Russ Allbery wrote:
>> If you put a config.cache file directly in the debian directory, you
>> probably know what you're doing and lintian shouldn't be warning about
>> it. That tag is designed to catch garbage
Russ Allbery wrote:
> * Show the N: line with a count of overrides per package by default and
> provide an option to suppress this output if someone wants.
> * Don't show the N: line by default and provide an option to turn it on.
How about counting them and output one N: line per invocation /
On Wed, Jan 02, 2008, Russ Allbery wrote:
> * Don't show the N: line by default and provide an option to turn it on.
I read a lot of people complain that the N: lines clutter the output:
lintian's colored output helps distinguishing clutter or the more
important errors from the harmless ones.
On Thu, Jan 03, 2008 at 12:21:54AM -0800, Russ Allbery wrote:
> > And yes, none of these are overrides to paper over lintian bugs... :)
> I dunno, I could make the argument that several of those are lintian bugs.
> *grin*
> O: samba source: configure-generated-file-in-source debian/config.cache
Steve Langasek <[EMAIL PROTECTED]> writes:
> E.g., this:
>
> N: samba_3.0.28-2.dsc overrode 4 warnings
> N: winbind_3.0.28-2_amd64.deb overrode 3 errors, 2 warnings
> N: smbfs_3.0.28-2_amd64.deb overrode 2 warnings
> N: samba-common_3.0.28-2_amd64.deb overrode 1 warning
> N: samba_3.0.28-2_am
Andreas Tille <[EMAIL PROTECTED]> writes:
> On Wed, 2 Jan 2008, Russ Allbery wrote:
>> After a recent problem with a package with a fairly egregious error
>> that was overridden, hurting the ability of the sponsor to notice it, I
>> added a line of output to the default lintian output saying if an
On Wed, Jan 02, 2008 at 10:30:09PM -0800, Russ Allbery wrote:
> After a recent problem with a package with a fairly egregious error that
> was overridden, hurting the ability of the sponsor to notice it, I added a
> line of output to the default lintian output saying if any package
> overrides erro
On Wed, 2 Jan 2008, Russ Allbery wrote:
After a recent problem with a package with a fairly egregious error that
was overridden, hurting the ability of the sponsor to notice it, I added a
line of output to the default lintian output saying if any package
overrides error or warning tags.
What a
On Wed, 02 Jan 2008, Russ Allbery wrote:
> > Currently on dpkg I have 4 N: lines: one per deb + one for the
> > .dsc. That clutters the output a bit too much to my taste. And ideally
> > it should be at the end of the output (or at the beginning) but not
> > spread in the output.
>
> I was going t
On Wed, 02 Jan 2008 22:30:09 -0800
Russ Allbery <[EMAIL PROTECTED]> wrote:
> After a recent problem with a package with a fairly egregious error that
> was overridden, hurting the ability of the sponsor to notice it, I added a
> line of output to the default lintian output saying if any package
>
Raphael Hertzog <[EMAIL PROTECTED]> writes:
> I agree. Although I think that it would be better if there could be a
> single line indicating overrides on everything that got scanned by
> lintian.
Hm, that's another option. That's kind of hard to do with the current
lintian architecture, I think,
On Thu, 03 Jan 2008, Luk Claes wrote:
> > * Show the N: line with a count of overrides per package by default and
> > provide an option to suppress this output if someone wants.
> >
> > * Don't show the N: line by default and provide an option to turn it on.
> >
> > Which should we do?
>
> We
On Wed, 2008-01-02 at 22:30 -0800, Russ Allbery wrote:
> After a recent problem with a package with a fairly egregious error that
> was overridden, hurting the ability of the sponsor to notice it, I added a
> line of output to the default lintian output saying if any package
> overrides error or wa
Hi Russ
Russ Allbery wrote:
> I'd really like to not have to make this decision myself. I'd like to get
> opinions and see if a consensus emerges. I personally always run lintian
> with -iI --show-overrides, so I'm clearly not the target audience for this
> feature one way or the other. Here ar
Russ Allbery <[EMAIL PROTECTED]> writes:
> Oh, and there are 1759 unused overrides in the archive in 369 packages.
> lintian -i will tell you about unused overrides. We do fix
> false-positive bugs!
lintian -I, rather. (Display info tags.)
--
Russ Allbery ([EMAIL PROTECTED])
After a recent problem with a package with a fairly egregious error that
was overridden, hurting the ability of the sponsor to notice it, I added a
line of output to the default lintian output saying if any package
overrides error or warning tags.
As I sort of suspected at the time, someone else h
26 matches
Mail list logo