Source: python-keyring Version: 16.1.0-1 User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:python3-defaults
[X-Debbugs-CC: debian...@lists.debian.org, python3-defau...@packages.debian.org] Dear maintainers, With a recent upload of python3-defaults (that switched the default python3 from 3.6 to 3.7) the autopkgtest of python-keyring 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.7.1-2 python-keyring from testing 16.1.0-1 all others from testing from testing I copied some of the output at the bottom of this report. The error points at the situation where python3.6-minimal is installed, but not python3.6. However, your autopkgtest uses $(py3versions -i) and assumes that the unittest module is installed, while it doesn't make sure that it is. Your autopkgtest should have a dependency on python3-all if you want to test all installed python3 versions (py3versions tells which python3.*-minimal versions are installed). More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-keyring/1399352/log.gz autopkgtest [05:52:44]: test secretstorage-python3: [----------------------- + cd /tmp/autopkgtest-lxc.b733xrs4/downtmp/autopkgtest_tmp + export XDG_RUNTIME_DIR=/tmp/autopkgtest-lxc.b733xrs4/downtmp/autopkgtest_tmp + py3versions -i + dbus-run-session -- python3.6 -m unittest -v keyring.tests.backends.test_SecretService /usr/bin/python3.6: No module named unittest autopkgtest [05:52:45]: test secretstorage-python3: -----------------------]
signature.asc
Description: OpenPGP digital signature