Hi, On 12/17/25 08:17, Sebastiaan Couwenberg wrote:
Our infra once should become smart enough for britney2 to extract that information, but we currently lack there.I know, I'm working on that. (#1120799)
As I told you there, britney2 would need to get access to d/t/control. The infrastructure for that isn't in place.
I expected that britney would schedule the CI jobs with doxygen & analizo from unstable already, because it seems to do that when new versions of the affected source packages are in unstable, just not when only binaries have newer versions in unstable.
It does that for most cases (that I'm aware of), but not for versioned *test* dependencies.
Maybe I should spend time on making britney also consider the results of CI jobs scheduled by others so we don't have bother you to schedule those.
It already does that. But as it doesn't consider these to be connected, it doesn't schedule them. I consider it correct behavior that britney2 only considers declared version relations. In this case it's just that test relations aren't considered.
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
