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

The need for Testsuite: autopkgtest in debian/control


I'm finding conflicting information on whether, with modern versions of
dpkg, maintainers supporting DEP-8 autopkgtests need to add a
Testsuite: autopkgtest header in debian/control.

The specification [1] says
   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.*
This seems to suggest that dpkg adds the entry to the source control
file (which seems wrong since dpkg should not modify debian/control),
but this may actually be conflating the source and binary control

This other reference documentation [2] says
   The fact that the package has a test suite must be declared by
   adding a Testsuite: autopkgtest entry to the source stanza in
It seems like probably the specification is misleading and the paragraph
should be clarified, except I don't know what it's trying to say.

[1] https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst
[2] https://ci.debian.net/doc/file.MAINTAINERS.html

Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: