Your message dated Sun, 13 Sep 2026 03:08:25 +0530
with message-id <[email protected]>
and subject line Re: Bug#1147535: lintian: the no-tests tag seems broken
has caused the Debian Bug report #1147535,
regarding lintian: the no-tests tag seems broken
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 [email protected]
immediately.)
--
1147535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1147535
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lintian
Severity: normal
I have not debugged this, but the no-tests tag seems broken.
1. Only 1 package triggers it [1], which seems highly improbable.
2. We don't have any tests it in the lintian codebase (it's one of the
'known-missing' tags). The fact none of the current test packages
triggers it also smells.
[1]: https://udd.debian.org/lintian-tag/no-tests?affected=yes
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau
⢿⡄⠘⠷⠚⠋ [email protected] / veronneau.org
⠈⠳⣄
--- End Message ---
--- Begin Message ---
On 13/09/26 12:44 am, Louis-Philippe Véronneau wrote:
> Package: lintian
> Severity: normal
>
> I have not debugged this, but the no-tests tag seems broken.
>
> 1. Only 1 package triggers it [1], which seems highly improbable.
This package has debian/tests as a "file". And apparently the logic in
`resolve_path` works in a way that when this happens, it switches to resolving
via parent directory.
So resolve_path('debian/tests/control') transforms into 'debian/control' for
this
particular package.
I've opened an MR to handle this very special case and will merge it after
pipeline
passes (change is simple).
> 2. We don't have any tests it in the lintian codebase (it's one of the
> 'known-missing' tags). The fact none of the current test packages
> triggers it also smells.
Actually, no-tests means something else here.
The description states
"""
Explanation: The autopackage test suite does not define any tests via
either the <code>Tests</code> field or the <code>Test-Command</code>
field.
See-Also:
https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst
"""
And this is the code in question
163 $self->pointed_hint('no-tests', $section_pointer)
164 unless $section->declares('Tests') ||
$section->declares('Test-Command');
So this means it flags things that *have* a d/t/control but do not have tests
declared there. I just
tried with some random stuff written into d/t/control and the package does not
seem to even *build*
with such a configuration.
So I suppose this is a redundant tag and can simply be dropped. Instead we
could have a new tag for
flagging packages without autopkgtests.
All that said, I am closing this bug report since the original concern is not
an actual issue.
>
> [1]: https://udd.debian.org/lintian-tag/no-tests?affected=yes
>
Best,
Nilesh
--- End Message ---
