release/1.9.0: Fix bug in awcli-v2, add upper bound for py-cryptography #511
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In var/spack/repos/builtin/packages/awscli-v2/package.py, add back in upper bound for py-cryptography. This matches the logic of awscli-v2 in spack develop, see: https://github.com/spack/spack/blame/e1b579a8b491b01579a24e18e520c27e7089f24f/var/spack/repos/builtin/packages/awscli-v2/package.py#L29C9-L29C66.
We don't need to worry about Python 3.12 for this version 2.15 of awscli-v2 anyway, NS newer versions of awscli-v2 will be available in the next release when we pull in spack develop, opening the door to move to Python 3.12 if we want to.
This fixes the following bug reported by @xian22: