Hi On 13-08-2025 12:57, Adrian Bunk wrote:
At what point is debian/control parsed to detect lines like Testsuite: autopkgtest-pkg-go ?
That's done in britney2.
At that point it should be possible to inject a test into every package that does something like Test-Command: lintian --fail-on error -T aliased-location /path/to/*.deb Restrictions: superficial
No, because the reading of the test suite is done on ci.d.n by /usr/bin/autopkgtest. So what would be needed is autopkgtest to get an interface to add tests from the outside, debci to grow an interface to accept the same information and pass it on to autopkgtest and britney2 to use that new debci interface.
What would you use as Test-Depends? I would naively say, all binaries, but what if not all binaries from one source are co-installable? Even if we'd solve that, /path/to/*.deb would be /var/cache/apt/archives/*.deb (but only those of the source under test). Can we rely on /var/cache? As an alternative, the test could download all the binaries *in* the test, but that feels clumsy for the 99% of the cases where we have just done so to install the Test-Depends of the other tests.
Oh, and autopkgtest uses autodep8 automatically. So packages in supported classes that haven't opted in to using that (e.g. because it doesn't work on their package) suddenly see themselves being tested and might fail.
Paul
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature