Bug#1088402: ansible integration test fail using aptsource
Package: python3-apt
Version: 2.6.0
Severity: normal
X-Debbugs-Cc: debian@rocketjump.eu
Hi,
ansible uses python3-apt in some of the integration tests, where it triggers
following traceback on sid:
Traceback (most recent call last):
File \"<stdin>\", line 121, in <module>
File \"<stdin>\", line 113, in _ansiballz_main
File \"<stdin>\", line 61, in invoke_module
File \"<frozen runpy>\", line 226, in run_module
File \"<frozen runpy>\", line 98, in _run_module_code
File \"<frozen runpy>\", line 88, in _run_code
File \"/tmp/ansible_apt_repository_payload_88mfa8n7/ansible_apt_repository_payload.zip/ansible/modules/apt_repository.py\", line 195, in <module>
File \"/usr/lib/python3/dist-packages/aptsources/distro.py\", line 547, in get_distro
release = os_release[\"VERSION_ID\"]
~~~~~~~~~~^^^^^^^^^^^^^^
KeyError: 'VERSION_ID'
The relevant code assumes that VERSION_ID is always set in /etc/so-release,
which is not the case for Debian sid. See Debian bugs #1042805, #746548 (requests
to add it in base-files). Upstream spec says the field is optional, so we can't
rely on it.
Greets,
Lee
-- System Information:
Debian Release: 12.8
APT prefers stable-updates
APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 'proposed-updates'), (990, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.11.5+bpo-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python3-apt depends on:
ii distro-info-data 0.58+deb12u3
ii libapt-pkg6.0 2.6.1
ii libc6 2.36-9+deb12u9
ii libgcc-s1 12.2.0-14
ii libstdc++6 12.2.0-14
ii python-apt-common 2.6.0
ii python3 3.11.2-1+b1
Versions of packages python3-apt recommends:
ii iso-codes 4.15.0-1
ii lsb-release 12.0-1
Versions of packages python3-apt suggests:
ii apt 2.6.1
pn python-apt-doc <none>
-- no debconf information
Reply to: