This is a multi-part message in MIME format.
Only replying to a snip of the replies but...
On 2025-05-23 13:48, Soren Stoutner wrote:
Lintian has dropped some tags that were considered inaccurate. Some have changed priority, so unless you are displaying Pedantic or Experimental you will no longer see them. And others have had their checks modified to minimize false positives, so they may no longer flag for your code base.
I personally check locally with:
lintian -iIE --pedantic
Then I choose to ignore Pedantic and Experimental tags that I don’t feel apply
to my project.
I do exactly what Soren does, at least with my local builds. I run every
build through an `sbuild` chroot that does lintian checks with `-iIE --pedantic` and then while I notice there's pedantic and informational
level errors, the vast majority of them I disregard. There are cases
where warnings or errors show up in the Lintian output that can be
specific to that Lintian version being out of date or where overrides
are needed, but informational, experimental, and pedantic I usually just
check locally and then determine if it needs addressed or not.
(I also check the source with Lintian, but since my main machine I
develop on is not the absolute latest, I always use the sbuild chroots
or chroots in general with updated lintian to run the lintian tests on.)
Thomas
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font face="Calibri">Only replying to a snip of the replies
but...</font></p>
<div class="moz-cite-prefix">On 2025-05-23 13:48, Soren Stoutner
wrote:<br>
</div>
<blockquote type="cite" cite="mid:3705694.hdfAi7Kttb@soren-desktop">
<pre class="moz-quote-pre" wrap="">Lintian has dropped some tags that were considered inaccurate. Some have
changed priority, so unless you are displaying Pedantic or Experimental you will no longer see them. And others have had their checks modified to
minimize false positives, so they may no longer flag for your code base.
I personally check locally with:
lintian -iIE --pedantic
Then I choose to ignore Pedantic and Experimental tags that I don’t feel apply
to my project.</pre>
</blockquote>
<p><span style="white-space: pre-wrap">I do exactly what Soren does, at least with my local builds. I run every build through an `sbuild` chroot that does lintian checks with `-iIE --pedantic` and then while I notice there's pedantic and
informational level errors, the vast majority of them I disregard. There are cases where warnings or errors show up in the Lintian output that can be specific to that Lintian version being out of date or where overrides are needed, but informational,
experimental, and pedantic I usually just check locally and then determine if it needs addressed or not.</span></p>
<p><span style="white-space: pre-wrap">(I also check the source with Lintian, but since my main machine I develop on is not the absolute latest, I always use the sbuild chroots or chroots in general with updated lintian to run the lintian tests on.)</
span></p>
<p><span style="white-space: pre-wrap">
</span></p>
<p><span style="white-space: pre-wrap">Thomas</span></p>
</body>
</html>
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)