IIRC this was a transient python bug in unstable. As I'm not able to reproduce this problem, and the version in experimental was also removed, I'm closing this bug.
On 30/11/2021 18:33, Marc Dequènes (duck) wrote: > Package: ansible > Version: 4.6.0-1 > Severity: important > > Quack, > > Despite the fix in #995879 it is not installable: > # apt install -t experimental ansible > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > The following additional packages will be installed: > ansible-core python3-resolvelib > Suggested packages: > cowsay sshpass > Recommended packages: > python3-kerberos python3-libcloud python3-winrm python3-xmltodict > The following NEW packages will be installed: > ansible-core python3-resolvelib > The following packages will be upgraded: > ansible > 1 upgraded, 2 newly installed, 0 to remove and 177 not upgraded. > Need to get 20.8 MB of archives. > After this operation, 67.6 MB of additional disk space will be used. > Do you want to continue? [Y/n] > Get:1 http://HTTPS///deb.debian.org/debian unstable/main amd64 > python3-resolvelib all 0.8.1-1 [25.4 kB] > Get:2 http://HTTPS///deb.debian.org/debian experimental/main amd64 > ansible all 4.6.0-1 [19.6 MB] > Get:3 http://HTTPS///deb.debian.org/debian unstable/main amd64 > ansible-core all 2.12.0-1 [1153 kB] > Fetched 20.8 MB in 5s (4339 kB/s) > Retrieving bug reports... Done > Parsing Found/Fixed information... Done > Reading changelogs... Done > apt-listchanges: Mailing root: apt-listchanges: news for Annael > Selecting previously unselected package python3-resolvelib. > (Reading database ... 553625 files and directories currently installed.) > Preparing to unpack .../python3-resolvelib_0.8.1-1_all.deb ... > Unpacking python3-resolvelib (0.8.1-1) ... > Preparing to unpack .../ansible_4.6.0-1_all.deb ... > Unpacking ansible (4.6.0-1) over (2.10.7+merged+base+2.10.8+dfsg-1) ... > Selecting previously unselected package ansible-core. > Preparing to unpack .../ansible-core_2.12.0-1_all.deb ... > Unpacking ansible-core (2.12.0-1) ... > Setting up python3-resolvelib (0.8.1-1) ... > Setting up ansible-core (2.12.0-1) ... > [Errno 2] No such file or directory: > '/usr/lib/python3.10/dist-packages/ansible/module_utils/ansible_release.py'dpkg: > error processing package ansible-core (--configure): > installed ansible-core package post-installation script subprocess > returned error exit status 1 > dpkg: dependency problems prevent configuration of ansible: > ansible depends on ansible-core (>= 2.11.5-1~); however: > Package ansible-core is not configured yet. > > dpkg: error processing package ansible (--configure): > dependency problems - leaving unconfigured > Processing triggers for man-db (2.9.4-2) ... > Errors were encountered while processing: > ansible-core > ansible > needrestart is being skipped since dpkg has failed > E: Sub-process /usr/bin/dpkg returned an error code (1) > > $ ls -l > /usr/lib/python3.10/dist-packages/ansible/module_utils/ansible_release.py > lrwxrwxrwx 1 root root 13 Nov 18 21:42 > /usr/lib/python3.10/dist-packages/ansible/module_utils/ansible_release.py -> > ../release.py > > But this file does not exist. > > I purged ansible and ansible-core, reinstalled and obtained the same > result. In fact upgrading or installing after purge does not change > anything. > > It seems this symlink is not owned by any package, is it generated??? > > I did not have time to dig deeper, hope that helps. > And thank for the hard work, the split seems to be a real pain in the > ass to handle. > > Regards. > \_o< >