On Thu, 29 Dec 2022 16:14:58 +0100
Hilmar Preuße <hille42@web.de> wrote:

An override has been added, but the line, which is found to be to
long seems to move, hence lintian complains or does not complain.

What do I do?

Use an asterisk (*) as a wildcard in the override, replacing the
details of the lintian hit that you don't really care about (such as
the line number, or the number of bytes on that particular line).

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEd8lhnEnWos3N8v+qQoMEoXSNzHoFAmOtt6AACgkQQoMEoXSN zHo0Yg//ZtyRaSya89EUkbnnqWhb5r+griv11VmsGfmGt2JDRKM8sC9DcztjgeKh BCmSuYOkpf9MNOnJcnrEt3bDV4JKnU7wWHuFqQTBSu+BSmunojWTl8swtAiaZBAu Vc5SaIbd9hrGvLdz6PCBj9Jvr6jGWQEgvgR06NvBV4s7IFrJwfPQ/TziQiCf7HYb y8nI6QrgB7qIHJZnGc4Mq8Cex0STwuo4IWfS1rBbHHc1JwYgcYi6v22aZtKsqHY7 H50RtPdnDan8cq3OwEjd+gTAm6nJmVCSBhbc/us4uvN9vGud3+6RRc7SNKHWXsH0 Cow5QK6CRtYUq0BZbQgLqm7flAStSEztfyVbvrq/xTy6T2TfVF2v23EfilsNDRpm Ndy/5F7EKk/248paZ3lTaJQHkXI3eg20MBzxdkCUsZe4nFv3fbcYN1tEGMhrn8B9 0fpUOmautSYfk7bbFJihcJacvvkELfZYKHJ9vLJoEE9zD8lNq3GoBBJI3S1XU9g7 OerW97DrGyyhroFv3dMgriwvYROZhxJ9EPm/mebejMpNPiF3WJnHBWjkAxuHrzWc eIJ4i1FK1h1uxiS9qY4+nWe2rh6DVTNXrtQAXXdwRVP27hBErLroU5iMCWbWv4eZ NcT9xtfhsfbl6FlzvANB1JrJ971kvmsnAF5xX3Aj02HLJ6Jz6zE=
=QhpF
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi all,

I'm just building Lintian overrides and I'm struggling with a test. Here
is the output of two lintian runs with unchanged source package, limited
to the interesting lines.

hille@sid-amd64:~/devel/TeXLive/github$ lintian --tag-display-limit 0 --pedantic -I texinfo_7.0.1-3.dsc
W: texinfo source: mismatched-override
very-long-line-length-in-source-file 1493 > 512 [tp/t/results/formats_encodings/at_commands_in_refs_utf8.pl:17317] [debian/source/lintian-overrides:23]
W: texinfo source: mismatched-override
very-long-line-length-in-source-file 617 > 512 [tp/t/results/sectioning/section_in_unnumbered_info.pl:6098] [debian/source/lintian-overrides:64]
P: texinfo source: very-long-line-length-in-source-file 1493 > 512 [tp/t/results/formats_encodings/at_commands_in_refs_utf8.pl:16903]
P: texinfo source: very-long-line-length-in-source-file 617 > 512 [tp/t/results/sectioning/section_in_unnumbered_info.pl:6548]
N: 0 hints overridden; 2 unused overrides

hille@sid-amd64:~/devel/TeXLive/github$ lintian --tag-display-limit 0 --pedantic -I texinfo_7.0.1-3.dsc
W: texinfo source: mismatched-override
very-long-line-length-in-source-file 1497 > 512 [tp/t/results/formats_encodings/at_commands_in_refs_latin1.pl:17317] [debian/source/lintian-overrides:24]
P: texinfo source: very-long-line-length-in-source-file 1497 > 512 [tp/t/results/formats_encodings/at_commands_in_refs_latin1.pl:16903]
N: 0 hints overridden; 1 unused override

An override has been added, but the line, which is found to be to long
seems to move, hence lintian complains or does not complain.

What do I do?

Hilmar
--
sigfault

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Am 29.12.2022 um 16:52 teilte Jeroen Ploemen mit:

On Thu, 29 Dec 2022 16:14:58 +0100
Hilmar Preuße <hille42@web.de> wrote:

Hi,

An override has been added, but the line, which is found to be to
long seems to move, hence lintian complains or does not complain.

What do I do?

Use an asterisk (*) as a wildcard in the override, replacing the
details of the lintian hit that you don't really care about (such as
the line number, or the number of bytes on that particular line).

Works, many thanks!

Would it make sense to open an issue at lintian?

Hilmar
--
sigfault

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Am 29.12.2022 um 18:41 teilte Hilmar Preuße mit:

Hi.

Works, many thanks!

Would it make sense to open an issue at lintian?

Done. #1027292 .

H.
--
sigfault

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)