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

Bug#924715: marked as done (lintian: Please rename the process based on what it is done (i.e. set $0))

Your message dated Thu, 28 May 2020 12:06:30 -0700
with message-id <CAFHYt56hfbxQ3x02nTjqyVgPEEpYwJB1=Op+iCYgJ2v5A+TxJw@mail.gmail.com>
and subject line Re: Bug#924715: lintian: Please rename the process based on what it is done (i.e. set $0)
has caused the Debian Bug report #924715,
regarding lintian: Please rename the process based on what it is done (i.e. set $0)
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.)


-- 
924715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924715
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: lintian
Version: 2.9.1
Severity: wishlist

Hi,

It is very useful when lintian changes its process name based on what
it is doing (in particularly when debugging things like #924714).
Though, only unpack jobs are currently the only parts that use this
feature.  Please expand it to more parts so it is easier to see what
is running amock.

Thanks,
~Niels

--- End Message ---
--- Begin Message --- 
Hi,

On Sat, Mar 16, 2019 at 2:48 AM Niels Thykier <niels@thykier.net> wrote:
>
> It is very useful when lintian changes its process name

Lintian only uses one process at the moment. The name currently
includes all arguments. It is set here:

    https://salsa.debian.org/lintian/lintian/-/blob/master/commands/lintian.pm#L541

Parallel execution of checks does not work presently (probably due to
a limitation in IO::Async) but the branch includes statements to set
the process IDs accordingly.

Closing this bug.

Kind regards
Felix Lechner

--- End Message ---
Reply to: