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

Bug#843662: marked as done (lintian.d.o: Missing visual clue for arch tags)

Your message dated Mon, 28 Jun 2021 16:54:57 -0700
with message-id <CAFHYt57ErmNFf-3mUWcNC7n2LnU0v6yPyyxdZCcNEnQbhVS8iQ@mail.gmail.com>
and subject line Re: lintian.d.o: Missing visual clue for arch tags
has caused the Debian Bug report #843662,
regarding lintian.d.o: Missing visual clue for arch tags
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.)


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

Missing manpages are reported twice in some cases:

https://lintian.debian.org/tags/binary-without-manpage.html

E.g. for 0install-core, 389-dsgw, aapt, abw2epub and many more.

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

> Missing manpages are reported twice in some cases:

The new lintian.d.o uses a PostgreSQL backend and shows only hints for
a particular port. (Hints are tag names plus identifying context.) We
currently generate runs only for 'amd64'. [1] The website's browser
interface may eventually offer a selection, if we generate hints for
other ports in the future. At this point, 'arm64' would be the most
likely candidate.

We do not currently aggregate results across ports as described in
earlier comments in this bug. That can be seen very clearly here [2]
but we may relax that at some point for overview pages if flipping
through multiple ports makes those pages too hard to read (overview
pages for single tags, for example). At that point, all hints on those
pages would probably show in which ports they were found. That would
allow a reader to ascertain immediately whether a tag occurred in the
wild—without having to flip through ports.

If you are okay with it, I am now closing this bug. Thanks!

Kind regards
Felix Lechner

[1] https://salsa.debian.org/lintian/detagtive/-/blob/master/node.js/routers/sources.js#L91
[2] https://salsa.debian.org/lintian/detagtive/-/blob/master/node.js/routers/tags.js#L129-142

--- End Message ---
Reply to: