Followup-For: Bug #968558
Package: ansible
Version: 2.7.7+dfsg-1
Dear Maintainer,
I confirm this bug for the following configuration. And I would like to
know whether there is a chance to get the fix from upstream
(https://github.com/ansible/ansible/pull/51909) in stable or not.
-- System Information:
Debian Release: 10.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-11-amd64 (SMP w/12 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages ansible depends on:
ii python3 3.7.3-1
ii python3-crypto 2.6.1-9+b1
ii python3-cryptography 2.6.1-3+deb10u2
ii python3-httplib2 0.11.3-2
ii python3-jinja2 2.10-2
ii python3-netaddr 0.7.19-1
ii python3-paramiko 2.4.2-0.1
ii python3-pkg-resources 40.8.0-1
ii python3-yaml 3.13-2
Versions of packages ansible recommends:
ii python3-jmespath 0.9.4-1
ii python3-kerberos 1.1.14-2
ii python3-libcloud 2.4.0-1
ii python3-selinux 2.8-1+b1
ii python3-winrm 0.3.0-2
ii python3-xmltodict 0.11.0-2
Versions of packages ansible suggests:
pn cowsay <none>
pn sshpass <none>
-- no debconf information
