Bug#779559: dpkg-source: Add test dependencies to .dsc

Adam Conrad adconrad at debian.org
Thu Mar 5 13:34:31 UTC 2015

On Wed, Mar 04, 2015 at 10:42:15AM +0100, Guillem Jover wrote:
> When I said coalesce any other dependencies I was thinking about the
> following situation. Say we have a package with an "autopkgtest"
> testsuite with dependencies «foo (>= 1.0), bar», and another "newchecks"
> testsuite with dependencies «quux, frob, bar». And then the
> Testsuite-Triggers ends up being «foo (>= 1.0), bar, quux, frob».

I'm not convinced this is actuall a problem.  What we're trying to
approximate here with auto-filling Testsuite-Triggers (rather than
someone specifying it manually in debian/control) is a set of packages
that we feel it would be reasonable to force a retest for.

Sure, maybe it wastes a few cycles if TestA doesn't actually depend
on or use DepB, but we run it when DepB changes anyway, but I'm not
sure optimising for that is worth having ${test}-Triggers instead of
just one concatenated field.

I suspect my opinion here is partially colored by issues of prettiness,
and I should probably not care about that, so if everyone else thinks
the shed should be red, I can go paint it that colour, and just pretend
it's blue in my mind.

... Adam

More information about the autopkgtest-devel mailing list