On Mon, 12 Oct 2026 11:44:23 +1100 Ben Finney <[email protected]> wrote:
> What is failing, evidently, is AutoPkgTest's step of copying the > Python package and test files, into its test environment. From > there, zero test cases are found, and the step fails. IIRC "testsuite: autopkgtest-pkg-pybuild" cannot handle doctests automagically, so you probably need a custom test setup. The tests are inside the module which is already installed into the global Python namespace and can be used right there. See jaraco.text and jaraco.context for ways to hack things into place. Neither will win a beauty contest, but it works. If you don't need to insert testdata or a conftest file, that would simplify things further and you might even be able to get away with just running "$py -m pytest --doctest-modules /usr/lib/python3/etc..." directly. > [1]: Within the SBuild session, the binary package is correct: > [...] > ./debian/python3-jaraco-logging/usr/lib/python3.14/dist-packages/jaraco/logging.py This path, with the Python version recorded in it, is wrong (the lintian run on the salsa CI already caught that too). FWIW: I've never come across a simple module package that needed a d/*.install file when using pybuild.
pgpvD7V47HDEI.pgp
Description: OpenPGP digital signature
