-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to install aws-cli via pip - package dependency broke #8036
Comments
I'm experiencing the same issue, suddenly it started failing with that error |
I have the same error while deploying my app via GitLab pipeline to AWS! |
Hi, same issue here, what version of setuptools you have ? |
Hi, same issue here with Python 3.11. Did you find any workaround? |
yaml/pyyaml#601 Also same issue here. Not sure what the best path forward is. Maybe can force an older version of cython when building pyyaml or wait for them to fix |
I'm switching to installing awscli via apt-get instead of pip now. |
For GitLab runner, I've switched to |
there is also the problem, and actually updating more than 800 gitlabci is not an option |
My team is having this issue as well. following for updates. |
Also moving to Alpine package, via |
also moving to apk add worked
|
I had the same problem when running |
Hi everyone, thanks for reporting the issue and workarounds you've found. The AWS CLI team has been actively looking into the issue and discussing potential workarounds and long-term solutions. Our recommended solution to unblock workflows is to upgrade to the AWS CLI v2. We understand that that's not straightforward for some users so if you need to stay on the AWS CLI v1, then using the We do not recommend installing an older version of PyYAML as PyYAML version 5.3.1 is associated with CVE-2020-14343 that was fixed in version 5.4. |
Thanks - for the quick response @hssyoo Given we don’t know the impact of replacing the AWS CLI v1 with V2 in bulk on these legacy system, I’ve tested the Thanks for the workaround. |
Hi everyone, thanks for your patience. We merged #8037 which extends our support for PyYAML 6.0. This is a partial solution as PyYAML 6.0 has wheels available for Python 3.10 and 3.11. This will not resolve issues for users on a platform with no PyYAML wheels (eg Alpine). You can see the list of available wheels for PyYAML 6.0 here: https://pypi.org/project/PyYAML/6.0/#files Another immediate workaround for users that need to stay on AWS CLI v1 is to download and install our bundled installer. |
Fix for users using Alpine here
|
This is the current latest version of the awscli. Attempts to solve a problem where the awscli was failing to install correctly. The problem was fixed in a recent version of the awscli: aws/aws-cli#8036 (comment) The awscli was previously pinned to a specific version due to a lack of support for Python 3.4/3.5: #549
Changes the `awscli` install step to always install the latest version. Essentially the inverse change to #549 where the `awscli` was pinned to a specific version due to a lack of support for Python 3.4/3.5 Attempts to solve a problem where the awscli was failing to install correctly. The problem was fixed in a recent version of the `awscli`: aws/aws-cli#8036 (comment)
Changes the `awscli` install step to always install the latest version. Essentially the inverse change to #549 where the `awscli` was pinned to a specific version due to a lack of support for Python 3.4/3.5 Attempts to solve a problem where the awscli was failing to install correctly. The problem was fixed in a recent version of the `awscli`: aws/aws-cli#8036 (comment)
Fix:
|
Hi @IamAmitE do you have any thoughts on how can I do this in a CI/CD env? I am installing ebcli for each build and I'm not sure how to specify pyyaml version in the virtualenv that ebcli_installer.py is setting up. I'm just running:
And getting the same |
I ran into the same issue. When you first run
I saw where it installed it. For me on Windows, it is installed in the following directory.
run: (May differ based off of OS) Then run the install after removing the code mentioned by @IamAmitE . |
The above didn't work for me. The only thing that did was to edit the eb installer script and add |
pip install awscli --break-system-packages |
Problem with AWS cli fixed by installing via apk instead of wget aws/aws-cli#8036 Problem with Maria DB client fixed by installing additional package as recommended: https://community.home-assistant.io/t/usr-lib-mariadb-plugin-caching-sha2-password-so-cannot-be-found/439973/7
Old builds were failing due to incompatible versions of PyYAML (which is a dependency of awscli) and cython_sources. This commit updates awscli to use v2 which is the suggested update here: aws/aws-cli#8036 (comment). This is a potentially breaking change.
Describe the bug
$ pip3 install awscli
Collecting awscli
Obtaining dependency information for awscli from https://files.pythonhosted.org/packages/43/9c/bf16d97f5de8aa4f9171c6c82bad0b4179921ddca5066ba980358da0e9a5/awscli-1.29.3-py3-none-any.whl.metadata
Downloading awscli-1.29.3-py3-none-any.whl.metadata (11 kB)
Collecting botocore==1.31.3 (from awscli)
Obtaining dependency information for botocore==1.31.3 from https://files.pythonhosted.org/packages/b0/f0/5755508b3305534cd4cf2a8a82bbbe42ee9d66fd2688be5ff3dfb85e9a99/botocore-1.31.3-py3-none-any.whl.metadata
Downloading botocore-1.31.3-py3-none-any.whl.metadata (5.9 kB)
Collecting docutils<0.17,>=0.10 (from awscli)
Downloading docutils-0.16-py2.py3-none-any.whl (548 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 548.2/548.2 kB 34.8 MB/s eta 0:00:00
Collecting s3transfer<0.7.0,>=0.6.0 (from awscli)
Downloading s3transfer-0.6.1-py3-none-any.whl (79 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 79.8/79.8 kB 12.2 MB/s eta 0:00:00
Collecting PyYAML<5.5,>=3.10 (from awscli)
Downloading PyYAML-5.4.1.tar.gz (175 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 175.1/175.1 kB 24.9 MB/s eta 0:00:00
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'error'
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> [62 lines of output]
running egg_info
writing lib3/PyYAML.egg-info/PKG-INFO
writing dependency_links to lib3/PyYAML.egg-info/dependency_links.txt
writing top-level names to lib3/PyYAML.egg-info/top_level.txt
/tmp/pip-build-env-vkrpwdkj/overlay/lib/python3.8/site-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in
setup.cfg
!!
note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
Expected Behavior
Install AWS cli
Current Behavior
errors out with dependency issues
Reproduction Steps
pip3 install awscli
Possible Solution
No response
Additional Information/Context
No response
CLI version used
1.29 (latest?)
Environment details (OS name and version, etc.)
linux gitlab runner
The text was updated successfully, but these errors were encountered: