Bug#1109680: release.debian.org: use lintian results to block testing migration

[Adrian Bunk <bunk@debian.org>]

On Wed, Aug 13, 2025 at 07:18:01AM +0200, Paul Gevers wrote:
> Hi Adrian,

Hi Paul,

> On 12-08-2025 22:05, Adrian Bunk wrote:
>...
> > Regarding the implementation, instead of waiting on another external
> > service that runs lintian it might be an option that britney
> > automatically adds an superficial autopkgtest to every package
> > running something line "lintian --fail-on error".
> 
> We already depend on udd, so that's not new.

udd is not new, but the service running lintian would be a new dependency.

> And even if we would pursue,
> how do you envision interaction of britney2 with autopkgtest to add that
> test? That's not supported on any of the levels, so that's quite a big
> change. And again, we only want to block on particular tags, not everything
> that lintian thinks it's wise to report.

At what point is debian/control parsed to detect lines like
  Testsuite: autopkgtest-pkg-go
?

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

> Paul

cu
Adrian