On Fri, 31 Jan 2025 at 18:45:22 +0100, Alexandre Detiste wrote:
> The very existence of "*/debian/tests/control: @builddeps@,"
> may contribute to hiding a lot of undeclared python3-pkg-res-sources
> dependencies,
> because it would be pulled-in anyway by python3-setuptools at autopkgtest
> but not at runtime.
This is one advantage of
Testsuite: autopkgtest-pkg-python
(which does a simple smoke-test without pulling in build-deps) over
Testsuite: autopkgtest-pkg-pybuild
(which has more thorough coverage by actually trying to run the upstream
test suite, but does pull in build-deps).
It is meant to be possible to declare
Testsuite: autopkgtest-pkg-python, autopkgtest-pkg-pybuild
and get the best of both worlds, and ideally many (most? all?) Python
modules would have both; but unfortunately that doesn't work due to
autodep8 limitations (#1042717, #1061620, #1077645).
https://salsa.debian.org/ci-team/autodep8/-/merge_requests/31 is one
attempt to fix that autodep8 limitation, but review feedback is that it
isn't quite right.
https://salsa.debian.org/ci-team/autodep8/-/merge_requests/33 is another
attempt to fix that autodep8 limitation, but at the cost of dropping
pattern-based auto-detection completely, and there is a concern that it
could regress test coverage for a significant number of packages.
I'm sorry that I cannot currently present a good solution to this.
smcv
