dpkg-source to automatically add a Testsuite field

Antonio Terceiro terceiro at debian.org
Tue Jul 8 14:22:57 UTC 2014

On Tue, Jul 08, 2014 at 03:06:14AM +0200, Guillem Jover wrote:
> > How will it handle an existing value in that field? In the future, we
> > might have other forms of test suite, thus requiring different items in
> > the Testsuite: field.  What happens when there is already
> > 
> >   Testsuite: foo
> > 
> > and dpkg-source detects the presence of debian/tests/control? Will it
> > merge `autopkgtest` into the list, or will it replace the existing
> > value?
> Ah indeed, here's the current behavior:
> The field is parsed as a comma-separated list of values (as per the
> spec). If the debian/tests/control file is present then the value will
> be added to the list. The values will always get emitted in alphabetical
> order as a comma-separated list, any dupes squashed, so that the output
> is reproducible. Unknown values are emitted untouched.
> If the field contains “autopkgtest”, but the debian/tests/control file
> is not present, then a warning will be issued, and the value preserved,
> as in “the maintainer knows better!?”. But maybe it is actually better
> to warn and just trim the “autopkgtest” value?
> Does this resolve your concern?



Antonio Terceiro <terceiro at debian.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/autopkgtest-devel/attachments/20140708/66adfe41/attachment.sig>

More information about the autopkgtest-devel mailing list