-
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
It's hard to package version 2 of aws-cli #5282
Comments
Hi @graywolf-at-work, thanks for your comment. I think that you are referring to this line in the https://github.com/aws/aws-cli/blob/v2/requirements.txt#L6 This refers to the tagged Could you make that request on the |
@kdaily FWIW, we're facing this problem with the Debian package of awscli: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970804 Since botocore v2 is breaking compatibility with botocore v1 (in addition to a lack of releases), I'd like to ask if it's possible to use awscli v2 with the old botocore? Does it require v2 specifically? |
I don't think using new awscli with old botocore makes sense, but it'd be helpful if it were possible to install the old and new botocore side-by-side. Would it be possible to address that before a release of botocore v2? |
Hi all, We recently published an update of what's happening with the AWS CLI. One of the things being worked on is a source distribution for the AWS CLI v2, which should help ease packaging. We'll update with more information once an implementation has been worked out. Thanks! |
Confirm by changing [ ] to [x] below:
Issue is about usage on:
Platform/OS/Hardware/Device
Archlinux, but this is platform-agnostic issue.
Describe the question
Currently it is really hard to track the aws-cli v2 for the purpose of packaging it. My steps basically are
and that works fine until there is an update to botocore, since at that
point it will stop being possible to install previous tags. I would like you
to consider making the dev versions in botocore actual tags, so that the
installation will work even after you release new version.
The exact same thing happend yeasterday, there was new botocore released
but 2.0.20 was not (yet), so in that interval it was just not possible to install
it.
But my python-fu is not the strongest, maybe there are flags to pip that would
solve this?
Logs/output
Get full traceback and error logs by adding
--debug
to the command.N/A
The text was updated successfully, but these errors were encountered: