Bug#852820: Testsuite-Restrictions field is hard to use
On Fri, 2017-01-27 at 15:58:28 +0000, Ian Jackson wrote:
> Package: dpkg-dev
> Version: 1.18.19
> >From the patch from Iain Lane:
> +This field declares the comma-separated union of all test restrictions
> +(\fBRestrictions\fP fields in \fIdebian/tests/control\fP file).
> This is quite awkward to use correctly, and is a hazard to correct
> implementation. For example, dgit's debian/tests/control contains
> several tests marked with Dgit-specific Restrictions with
> x-dgit-... names. The result is that with 1.18.10ubuntu1, we would
> see this in dgit's .dsc:
> Testsuite-Restrictions: x-dgit-intree-only x-dgit-git-only x-dgit-schroot-build
> If not interpreted very carefully, this would give a test suite runner
> the erroneous impression that none of the tests can be run.
Right, I see what you mean.
> Also, Iain's stated use case in #847926 does not require anything new
> in the .dsc and hence Sources.gz. All that is required to get the
> full information (debian/tests/control) is to extract the source
> package. That extraction of the source package has to be done anyway
> no matter how the tests will be run.
OTOH, the same could be said for several of the fields in the .dsc, such
as Build-Depends, but we still list them because it's more convenient to
not have to extract the source beforehand.
> If we do need more information in Sources.gz then maybe the set of
> combinations of restrictions ought to be listed. But then the
> features might be useful too.
> I'm sorry that I'm reporting this bug now, due to happening to see the
> message on debian-dpkg. But really I think:
> * Changes to the .dsc format and hence to the Sources format should
> be discussed more widely than a bug on debian-dpkg.
> * Changes to the handling of autopkgtest (DEP-8) metadata should be
> discussed on autopkgtest-devel (or other DEP-8 related places).
TBH, I hesitated a bit before adding this, because this percolates
into many other places. But considered that, while the information
could be retrieved in other ways, it made life easier for test
runners. And we can always remove it if it ends up being
But I certainly agree that this should have probably been discussed
more widely, which is something I overlooked, sorry about that. And
agree completely with your two points above. So I'll be adding an
entry to the FAQ detailing the process to add new information to
the .dsc file (and probably to the .changes and other interchange