Bug#1120799: release.debian.org: CI job scheduling is not aware of transitions

[Sebastiaan Couwenberg <sebastic@debian.org>]

On 11/25/25 7:22 AM, Paul Gevers wrote:
> On 11/25/25 05:45, Sebastiaan Couwenberg wrote:
> > I don't see how we can do without d/t/control to get the test dependencies, those tend to be similar to Build-Depends and Depends but they are not the same, and the test dependencies are not available in Sources.gz or Packages.gz
>
> They are added to Sources via the Testsuite-Triggers field, which exists for this purpose. And yes, some information is stripped that way. There are multiple reasons why I'd want britney2 to have access to all d/t/control stanza (or at least a richer data set than Testsuite-Triggers) but I don't think it's needed for this bug.

Testsuite-Triggers is not very useful as it's missing for packages using autodep8 (those with Testsuite: autopkgtest-pkg-<type>).

The best we can do without parsing autodep8 output is to mimic ben and resolve the dependencies for the arch:any binary packages of the source package in question.

Kind Regards,

Bas

--
 PGP Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1