Noticed that the latest version of ade (26.8.0) was failing to detect that dependencies already installed in the venv were present, causing editable installs to always fail with [ERROR]: Failed to resolve the requested dependencies map. Could not satisfy the following requirements.
For example, something like this:
$ ade install -e ./ansible_collections/namespace/collection1
Critical: Failed to install collection dependencies: Got 1 return code from: /usr/local/bin/ansible-galaxy collection install
stdout:
Starting galaxy collection install process
Process install dependency map
stderr:
[ERROR]: Failed to resolve the requested dependencies map. Could not satisfy the following requirements:
* namespace.collection2:>=1.0.0,<2.0.0 (direct request)
Hint: Pre-releases hosted on Galaxy or Automation Hub are not installed by default unless a specific version is
requested. To enable pre-releases globally, use --pre:
Even though namespace.collection2 is already present if you do ade list.
Rolling back to ansible-dev-environment==26.6.1 solved the problem.
Noticed that the latest version of ade (26.8.0) was failing to detect that dependencies already installed in the venv were present, causing editable installs to always fail with
[ERROR]: Failed to resolve the requested dependencies map. Could not satisfy the following requirements.For example, something like this:
Even though
namespace.collection2is already present if you doade list.Rolling back to
ansible-dev-environment==26.6.1solved the problem.