IIRC this was added because the last python transition (3.9->3.10) broke
the autopkgtests, so I've added it. As this seems to work this time
around, I acknowledge the NMU.
On Tue, 10 Jan 2023 08:21:09 -0800 Steve Langasek
<steve.langa...@canonical.com> wrote:
Package: ansible-core
Version: 2.14.1-1
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar ubuntu-patch
Hi Lee,
The ansible-core autopkgtests fail now that /usr/bin/python3 is python 3.11:
[...]
autopkgtest [08:17:06]: test unit: [-----------------------
FATAL: Running under Python version 3.11 instead of 3.10.
FATAL: Command "/usr/bin/env
ANSIBLE_TEST_CONTENT_ROOT=/tmp/autopkgtest-lxc.8ik95lf6/downtmp/build.jHa/src
PYTHONPATH=/tmp/ansible-test-iin32i73 /usr/bin/python3 /usr/bin/ansible-test units
--containers '{}' --truncate 0 --color no --host-path test/results/.tmp/host-n2w5rzai
--metadata test/results/.tmp/metadata-_yj0am3d.json" returned exit status 1.
autopkgtest [08:17:07]: test unit: -----------------------]
[...]
(https://ci.debian.net/data/autopkgtest/unstable/amd64/a/ansible-core/29976247/log.gz)
This comes down to a hard-coded "--python 3.11" option in the autopkgtest
which seems superfluous.
I have uploaded the attached patch to Ubuntu to unblock the python3-defaults
transition there.
Cheers,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
