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
{{ message }}
This repository has been archived by the owner on Jul 18, 2024. It is now read-only.
I've created my environment with make setup a week ago, today I got the following build error after a make clean:
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
awscli 1.21.4 requires botocore==1.22.4, but you have botocore 1.22.9 which is incompatible.
The error is raised during installing the dependency from ecom.
I've fixed this issue by upgrading the awscli manually with pip3 install --upgrade awscli, below you can find the pip3 list outputs before and after the upgrade.
It seems that during the build the latest version of botocore is used if boto3 in /shared/ecom/requirements.txt is installed but not the latest version of awscli from /requirements.txt.
Maybe it is possible to fix the dependency versions to avoid this error. If this is not possible there should be hint in the documentation how to upgrade the awscli manually.
I've created my environment with
make setup
a week ago, today I got the following build error after amake clean
:The error is raised during installing the dependency from ecom.
I've fixed this issue by upgrading the awscli manually with
pip3 install --upgrade awscli
, below you can find thepip3 list
outputs before and after the upgrade.It seems that during the build the latest version of botocore is used if boto3 in /shared/ecom/requirements.txt is installed but not the latest version of awscli from /requirements.txt.
Maybe it is possible to fix the dependency versions to avoid this error. If this is not possible there should be hint in the documentation how to upgrade the awscli manually.
Before upgrade:
After upgrade
The text was updated successfully, but these errors were encountered: