[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#660733: marked as done (lintian.debian.org: Do a "one-time" runs of trial checks on lintian.d.o?)

Your message dated Sat, 25 Sep 2021 20:36:23 -0700
with message-id <CAFHYt54Uk7N2zzacYMjqB+y-1Q=ttBcsEvKffEnLdxvLQ2y0dA@mail.gmail.com>
and subject line Re: lintian.debian.org: Do a "one-time" runs of trial checks on lintian.d.o?
has caused the Debian Bug report #660733,
regarding lintian.debian.org: Do a "one-time" runs of trial checks on lintian.d.o?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
660733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660733
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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).

--- End Message ---
--- Begin Message --- 
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

--- End Message ---
Reply to: