You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now it's possible to specify a specific ansible-core or ansible-runner version, but it's not possible to specify any constraints on their dependencies (or if there is, I didn't find it).
This causes a big problem right now because python-daemon 3.0.2 (a dependency of ansible-runner) breaks setuptools (https://pagure.io/python-daemon/issue/94), which breaks every single EE build that installs a Python dependency that uses setup.py / setup.cfg - and there's no way to avoid it since it's apparently not possible to tell ansible-builder to pin python-daemon to != 3.0.2.
(Maybe you can prepend build steps to manually install another version before ansible-builder calls pip, but I consider that a hack, not a good solution.)
The text was updated successfully, but these errors were encountered:
(python-daemon 3.0.2 has been yanked, so that specific problem is solved, but having a way to pin or constrain dependencies is still a good thing to have :) )
Right now it's possible to specify a specific ansible-core or ansible-runner version, but it's not possible to specify any constraints on their dependencies (or if there is, I didn't find it).
This causes a big problem right now because python-daemon 3.0.2 (a dependency of ansible-runner) breaks setuptools (https://pagure.io/python-daemon/issue/94), which breaks every single EE build that installs a Python dependency that uses setup.py / setup.cfg - and there's no way to avoid it since it's apparently not possible to tell ansible-builder to pin python-daemon to != 3.0.2.
(Maybe you can prepend build steps to manually install another version before ansible-builder calls pip, but I consider that a hack, not a good solution.)
The text was updated successfully, but these errors were encountered: