Debian Bug report logs - #660733
lintian.debian.org: Do a "one-time" runs of trial checks on lintian.d.o?

Toggle useless messages

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

From: Niels Thykier <niels@thykier.net>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: [reporting/harness]: do "one-time" runs of trial checks on lintian.d.o?

Date: Tue, 21 Feb 2012 12:13:02 +0100

Package: lintian
Severity: wishlist

This suggestion is based on #367466 comment 22 and also on some thoughts
I did when we added the perl4-libs warning.

The basic idea would be to "inject" extra checks in the standard lintian
run, but filter the tags into a separate log file[1].  Together with a
fix for #660732 we could get "full run" sample of that check.

We may want to restrict "droping of checks" to (checks reviewed by)
Lintian maintainers[2].  It is also possible we want to fix #359059 first.

~Niels

[1] How the "injection" would work in practise ... is an exercise left
for the reader/implemented/etc.

[2] Else a faulty unannounced check could DoS lintian.d.o for days (e.g.
by entering endless loop).

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

From: Niels Thykier <niels@thykier.net>

To: 660733@bugs.debian.org

Subject: Re: [reporting/harness]: do "one-time" runs of trial checks on lintian.d.o?

Date: Thu, 14 May 2015 09:43:14 +0200

On Tue, 21 Feb 2012 12:13:02 +0100 Niels Thykier <niels@thykier.net> wrote:
> Package: lintian
> Severity: wishlist
> 
> This suggestion is based on #367466 comment 22 and also on some thoughts
> I did when we added the perl4-libs warning.
> 
> The basic idea would be to "inject" extra checks in the standard lintian
> run, but filter the tags into a separate log file[1].  Together with a
> fix for #660732 we could get "full run" sample of that check.
> 
> We may want to restrict "droping of checks" to (checks reviewed by)
> Lintian maintainers[2].  It is also possible we want to fix #359059 first.
> 
> ~Niels
> 
> [1] How the "injection" would work in practise ... is an exercise left
> for the reader/implemented/etc.
> 
> [2] Else a faulty unannounced check could DoS lintian.d.o for days (e.g.
> by entering endless loop).
> 
> 

With the recent harness refactoring, we can trivially reschedule a
complete recheck of all packages[1].  If we were to do "injected" tags
as "experimental" ones, there will probably not be a major issue if they
appeared on the resulting website.

 * What really remains, is a good infrastructure to pull extra checks
   on lindsay.d.o.

~Niels

[1]: rm -f harness-state/state-cache

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

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

To: 660733-done@bugs.debian.org, Niels Thykier <niels@thykier.net>

Subject: Re: lintian.debian.org: Do a "one-time" runs of trial checks on lintian.d.o?

Date: Sat, 25 Sep 2021 20:36:23 -0700

Hi,

> "inject" extra checks in the standard lintian
> run, but filter the tags into a separate log file[1].
>
> a good infrastructure to pull extra checks
>
> we could get "full run" sample of that check.

I believe that functionality is no longer needed. The new website is
powered by a PostgreSQL database. The runners process files in the
archive when appropriate, such as:

    - upload of a new package version
    - availability of a new Lintian version.

The new website uses Lintian from Git. New tags can be tried out by
pushing a new commit before cutting a release.

For disputed tags like unmerged-usr, it's best to use a
'classification' level. Those tags are not shown to users but are
available from the website's JSON interface, which is very easy to
use.

Closing this bug.

Kind regards
Felix Lechner

Send a report that this bug log contains spam.