Debian Bug report logs - #512901
lintian: Show override comments on lintian.d.o

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Paul Wise <pabs@debian.org>

To: submit@bugs.debian.org

Subject: lintian: show override comments in the html?

Date: Sun, 25 Jan 2009 08:07:57 +1100

[Message part 1 (text/plain, inline)]

Package: lintian
Severity: wishlist

Is it possible to show comments from the override file on the web? 

For example, /usr/share/lintian/overrides/apt contains this:

# apt-mark is rarely used auxiliary script, we don't want to depend on
# python-apt only for it. 
apt binary: python-script-but-no-python-dep ./usr/bin/apt-mark

But this isn't shown here:

http://lintian.debian.org/tags/python-script-but-no-python-dep.html

Would it be possible to make it look something like this:

apt (binary) overridden
      * O ./usr/bin/apt-mark
     apt-mark is rarely used auxiliary script, we don't want to depend
     on python-apt only for it.

The comments between lintian tags in the override file could be saved
and added to the next lintian tag that comes along. This will require
some parsing but shouldn't be too hard to add.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise

[signature.asc (application/pgp-signature, inline)]

Message #12 received at 512901-quiet@bugs.debian.org (full text, mbox, reply):

From: Raphael Geissert <atomo64@gmail.com>

To: 474590@bugs.debian.org, 512901-submitter@bugs.debian.org, 512901-quiet@bugs.debian.org

Cc: control@bugs.debian.org

Subject: [frontend] add a parsable reason for overrides and optionally require it

Date: Wed, 11 Feb 2009 23:57:22 -0600

[Message part 1 (text/plain, inline)]

block 512901 with 474590
thanks

Hi all,

After thinking for a while about how to implement 474590 I think an approach 
like the one propposed in 512901 would be the best. This is based on two 
points:
* First, comment lines are already supported: adding something on the same 
line as the tag would break old lintians, and we don't want that. Introducing 
some other sort of comment lines would have the same effect.
* Second, I don't remember seeing any override file with comments where the 
comments were below the tag line.

My proposed parsing would then be:
# Comment explaining why the below tag is overridden
T: package: tag [extra [...]]
# Explanation for the following overrides, this comment
# should be re-used for the same tags, as duplicating the same information
# over and over again is useless. But it shouldn't be re-used for "bar-tag",
# nor any other tag other than "foo-tag"
T: package: foo-tag [extra [...]]
T: package: foo-tag [extra [...]]
T: package: bar-tag [extra [...]]

In order to properly implement/integrate #512901 maybe we should ask Jordà 
Polo to help us a bit, unless somebody wants to play with the reporting 
scripts :).

The implementation of #512901 is still a bit tricky because the comments need 
to be made available next to the overridden tags when --show-overrides is 
used so that reporting/harness sees them. Russ or anyone else: is there any 
suggestion on what letter to use to indicate that they are comments? "C"? 
another possibility would be to print them as "N" with some sort of format 
that harness could identify and parse.

Suggestions? Comments?

Cheers,
-- 
Raphael Geissert - Debian Maintainer
www.debian.org - get.debian.net

[signature.asc (application/pgp-signature, inline)]

Message #20 received at 512901-quiet@bugs.debian.org (full text, mbox, reply):

From: Russ Allbery <rra@debian.org>

To: 474590@bugs.debian.org, 512901-submitter@bugs.debian.org, 512901-quiet@bugs.debian.org

Subject: Re: Bug#474590: [frontend] add a parsable reason for overrides and optionally require it

Date: Wed, 11 Feb 2009 22:10:24 -0800

Raphael Geissert <atomo64@gmail.com> writes:

> The implementation of #512901 is still a bit tricky because the comments
> need to be made available next to the overridden tags when
> --show-overrides is used so that reporting/harness sees them. Russ or
> anyone else: is there any suggestion on what letter to use to indicate
> that they are comments? "C"?  another possibility would be to print them
> as "N" with some sort of format that harness could identify and parse.
>
> Suggestions? Comments?

I think using N: with some special marker is the best idea, but that's
only a tentative opinion and I could be convinced otherwise.

The rest of your idea seems quite sound to me.

-- 
Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>

Message #50 received at 512901-done@bugs.debian.org (full text, mbox, reply):

From: Felix Lechner <felix.lechner@lease-up.com>

To: 512901-done@bugs.debian.org

Cc: Paul Wise <pabs@debian.org>, Raphael Geissert <atomo64@gmail.com>, Russ Allbery <rra@debian.org>

Subject: Re: lintian: Show override comments on website

Date: Fri, 21 Aug 2020 19:01:03 -0700

Hi,

The lintian.d.o website now shows override comments. So does the
standalone HTML page generated for Salsa CI.

This bug is now closed.

Kind regards
Felix Lechner

Send a report that this bug log contains spam.