On Mon, 07 Dec 2020 16:07:46 +0200, Andrius Merkys wrote:
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.
Out of curiosity: Why? [0]
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'. Am I doing something wrong, or is this an issue
with lintian?
I think I've seen this before, and so far I've ignored it (or maybe overridden it) as "well, yes, this is a special situation …"
But maybe lintian could be improved, I never really looked into the
details of this combination.
[0]
We do have some packages like this:
% ls -1d */debian/tests/control
boxer/debian/tests/control
debsums/debian/tests/control
equivs/debian/tests/control
lemonldap-ng/debian/tests/control libapache-authenhook-perl/debian/tests/control libapache-ssllookup-perl/debian/tests/control libapache2-mod-perl2/debian/tests/control libapache2-reload-perl/debian/tests/control libcli-framework-perl/debian/tests/control libdbd-mariadb-perl/debian/tests/control libdbd-mysql-perl/debian/tests/control
libdist-inkt-perl/debian/tests/control
mb2md/debian/tests/control
(Although some of them would probably be fine with a default autopkgtest-pkg-perl. Others are applications and not typical CPAN distributions/modules, and others really need special casing.)
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'. Am I doing something wrong, or is this an issue
with lintian?
The package in question (libjson-validator-perl) is to provide symlinksI am working on a package already having pkg-perl autopkgtest suite, and >> with 'Testsuite: autopkgtest-pkg-perl' in d/control. I want to add aOut of curiosity: Why? [0]
regular autopkgtest in addition to already existing pkg-perl suite.
to files in another binary package (openapi-specification) [1]. With
this autopkgtest I want to make sure the symlinks are not broken by
changes in openapi-specification.
But maybe lintian could be improved, I never really looked into theBy looking into lintian code [2], it seems that the code expects
details of this combination.
'Testsuite' to contain a single entry, not comma-separated entries. I
will file an issue on lintian.
https://salsa.debian.org/ci-team/autopkgtest/raw/master/doc/README.package-tests.rst
says:
Source package header
---------------------
To allow test execution environments to discover packages which provide
tests, their source packages need to have a ``Testsuite:`` header
containing ``autopkgtest`` (or a value like ``autopkgtest-pkg-perl``,
see below). Multiple values get comma separated, as usual in control
files. This tag is added automatically by dpkg-source version 1.17.11
or later, so normally you don't need to worry about this field.
so it looks like more than one values are indeed allowed.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 84:02:06 |
Calls: | 6,658 |
Calls today: | 4 |
Files: | 12,203 |
Messages: | 5,333,599 |
Posted today: | 1 |