FS#73390 - [molecule] broken due to python-ansible-compat dependency update
Attached to Project:
Community Packages
Opened by gardar (gardar) - Monday, 17 January 2022, 10:25 GMT
Last edited by David Runge (dvzrv) - Tuesday, 18 January 2022, 08:48 GMT
Opened by gardar (gardar) - Monday, 17 January 2022, 10:25 GMT
Last edited by David Runge (dvzrv) - Tuesday, 18 January 2022, 08:48 GMT
|
Details
Description:
Molecule is currently broken as it depends on python-ansible-compat>=0.5.0 but the python-ansible-compat package has been updated to 1.0.0. This has already been fixed in the main branch of molecule but a new release has not been made yet: https://github.com/ansible-community/molecule/pull/3392 Additional info: * package version(s) * config and/or log files etc. * link to upstream bug report, if any https://github.com/ansible-community/molecule/pull/3392 Steps to reproduce: |
This task depends upon
Closed by David Runge (dvzrv)
Tuesday, 18 January 2022, 08:48 GMT
Reason for closing: Fixed
Additional comments about closing: Seems the python-setuptools-scm and python-setuptools-scm-git-archive packages are makedepends. Fixed with 1.0.0-2
Tuesday, 18 January 2022, 08:48 GMT
Reason for closing: Fixed
Additional comments about closing: Seems the python-setuptools-scm and python-setuptools-scm-git-archive packages are makedepends. Fixed with 1.0.0-2
Python-ansible-compat 1.0.0 *should* satisfy the >= 0.5.0 requirement.
However, looking at /usr/lib/python3.10/site-packages/ansible_compat-0.0.0.dist-info/METADATA we can observe that the package declares itself as `Version: 0.0.0`.
So much for "it'll be completely fiiiiine to drop setuptools" (this issue is because I need to use "new" but more complicated and more error prone ways of building and installing python-ansible-compat because upstream chose to remove setup.py integration). If you are using a lot of Python programs, get ready for a whole lot more to break in the coming months. ;-)