Re: ROCm CI: Scheduling for experimental active again

[Christian Kastner <ckk@debian.org>]

Sorry, it's late and I goofed up.

On 2024-01-10 23:39, Christian Kastner wrote:
> For any given source package A, the resolver
>   (1) looks at all binary packages built by A
>   (2) collects all there reverse binary dependencies
                     their*
>   (3) for all binary packages collected in (2), find source packages
>   (4) for all source packages found in (3), repeat from (1)

This describes how *reverse* dependencies affected by changes are
resolved, not dependencies which trigger tests.

But the steps are pretty similar in the dependency case, with (4)
omitted (we don't recurse on dependencies):
  (1) look at all binary packages built by A
  (2) collect all their dependencies (from the Depends: field)
  (3) for all binary packages collected in (2), find source packages

So the proposed change still works: fix step (1).

Good night,
Christian