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

Bug#976801: lintian: team/pkg-perl/testsuite/no-team-tests does not consider multi-valued Testsuite field



Package: lintian
Version: 2.104.0

Hello,

Tag team/pkg-perl/testsuite/no-team-tests does not seem to consider
multi-valued Testsuite field. The same issue may also be in pkg-js, but
this I have not checked.

I am working on a package already having pkg-perl autopkgtest suite, and
with 'Testsuite: autopkgtest-pkg-perl' in d/control. I want to add a
regular autopkgtest in addition to already existing pkg-perl suite. I
add d/tests/control with a 'Test-Command' there, but now lintian
complains with:

team/pkg-perl/testsuite/no-team-tests autopkgtest, autopkgtest-pkg-perl

The same tag is shown even if I change to 'Testsuite: autopkgtest,
autopkgtest-pkg-perl'.

Looking at lintian's code it seems it emits this tag whenever explicit
or implicit value of Testsuite is not autopkgtest is not equal to
'autopkgtest-pkg-perl'. What I expect is that lintian checks for any of
the comma-separated Testsuite values equal to 'autopkgtest-pkg-perl'.

Debian policy on the d/control Testsuite field [1]:

5.6.30. Testsuite

Simple field containing a comma-separated list of values allowing test
execution environments to discover packages which provide tests.

This field is automatically added to Debian source control files (.dsc)
by dpkg, with the value autopkgtest, when a debian/tests/control file is
present in the source package. This field may also be used in source
package control files (debian/control) if needed in other situations.

[1] https://www.debian.org/doc/debian-policy/ch-controlfields.html#testsuite

Best,
Andrius


Reply to: