On Mon, 07 Dec 2020 17:01:05 +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] > The package in question (libjson-validator-perl) is to provide symlinks > 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. Ah, right, I also just saw your commit. An additional test seems useful indeed. > > But maybe lintian could be improved, I never really looked into the > > details of this combination. > By looking into lintian code [2], it seems that the code expects > '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. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Neil Young: There's A World
Attachment:
signature.asc
Description: Digital Signature