On 12/17/25 10:13 PM, Paul Gevers wrote:
On 12/17/25 19:12, Sebastiaan Couwenberg wrote:
I'm afraid that a proper solution requires access to d/t/control of the source
packages, are you aware what makes that difficult to make available?
I don't know, but I can imaging we don't want all the sources there if all we
need is d/t/control files.
I personally would like the test dependencies to move from d/t/control to
Test-Depends in d/control (and be available in Sources alongside
Build-Depends*), but then you lose the granularity per test.
And it raises questions one how that interacts with <!nocheck> Build-Depends.
Being more liberal in pulling dependencies from unstable in newer version are
available could be a solution too,
I think we strike a reasonable balance.
The current situation is not something I consider reasonable, RT intervention
in required far too often for situations that should be handled automatically.
Like the autopkgtest scheduling being completely unaware of transition.
I have a script [0] that get a lists of dependencies that have newer versions
in unstable.
And I think this is too much. Then we might as well just test in unstable
instead of in testing.
That's not the purpose of that script, it's to experiment with python-apt to
find newer dependencies in unstable.
As I mentioned in reply to Adrian [0], pulling everything from unstable is the
far end of being more liberal in pulling dependencies from unstable and not
what I'm considering.
What do you think about the scenario I described in that post?
[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1123074#50
My suggestion is to let DDs schedule CI jobs with additional pin for
dependencies in unstable, and have britney2 consider these results for the
excuses instead of only the CI jobs it scheduled itself.
In my interactions, I often had to explain what we try to achieve and why we're
often asking maintainers to fix their packages. Doing the above would, I fear,
leave too much room for people to paper over things we don't want to be paper
over. I rather opt for you asking me for help in the cases where britney2
doesn't do the right thing.
And then people run out of patience and remove the autopkgtest because it
hinders testing migration more than it helps.
Kind Regards,
Bas
--
PGP Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
