Source: python-duckpy Version: 3.2.0-1 Severity: serious X-Debbugs-CC: firstname.lastname@example.org Tags: sid bookworm User: email@example.com Usertags: needs-update User: firstname.lastname@example.org Usertags: python3.10 Control: affects -1 src:python3-defaults Dear maintainer(s),We are in the transition of adding python3.10 to the supported Python versions . With a recent upload of python3-defaults the autopkgtest of python-duckpy fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form:
pass fail python3-defaults from testing 3.9.8-1 python-duckpy from testing 3.2.0-1 all others from testing from testingI copied some of the output at the bottom of this report. It seems the test tries to test for all supported Python3 versions, but fails to ensure all those versions are actually installed during the test. E.g. a test dependency on python3-all (or one of its siblings).
Currently this regression is blocking the migration of python3-defaults to testing . https://docs.python.org/3/whatsnew/3.10.html lists what's new in Python3.10, it may help to identify what needs to be updated.
More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul  https://bugs.debian.org/996584  https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-duckpy/17574738/log.gzTesting with python3.10 in /tmp/autopkgtest-lxc.hmzefuht/downtmp/autopkgtest_tmp: /tmp/autopkgtest-lxc.hmzefuht/downtmp/build.d02/src/debian/tests/run-unit-test: line 19: python3.10: command not found
autopkgtest [06:11:09]: test run-unit-test
Description: OpenPGP digital signature