| Git Clone URL: | https://aur.archlinux.org/aws-cli-v2.git (read-only, click to copy) |
|---|---|
| Package Base: | aws-cli-v2 |
| Description: | Unified command line interface for Amazon Web Services (version 2) |
| Upstream URL: | https://github.com/aws/aws-cli/tree/v2 |
| Licenses: | Apache-2.0 |
| Conflicts: | aws-cli |
| Provides: | aws-cli |
| Submitter: | jelly |
| Maintainer: | kstolp |
| Last Packager: | kstolp |
| Votes: | 28 |
| Popularity: | 4.31 |
| First Submitted: | 2024-04-21 11:04 (UTC) |
| Last Updated: | 2024-11-21 03:58 (UTC) |
@kino_t Thank you, I'm glad for you, but I was directing my comment to whom I was quoting - @VLegacy.
It has been established that tests sometimes fail based on the environment, first with my issues with DST, and then with VLegacy's issues with his environment variables. It's expected that they might pass in other people's environments.
@asday All tests passed on my machine.
The checks still fail unless I unset the AWS_DEFAULT_PROFILE environment variable in my shell prior to running the update.
That sounds like an upstream bug to me - do they still fail in the same manner and are they fixable in the same manner with a clean checkout not involving the AUR? If so, I'd recommend opening an issue on the github.
The latest package update to reduce the number of parallel workers used by pytest in the checks is a huge improvement to the system load problem. Thank you!
The checks still fail unless I unset the AWS_DEFAULT_PROFILE environment variable in my shell prior to running the update. I see that the setup for the checks set AWS_SECRET_ACCESS_KEY and AWS_ACCESS_KEY_ID to fake values prior to running the tests. Perhaps it could also unset AWS_DEFAULT_PROFILE to avoid the user's environment variable from being used in the tests and causing issues?
Joining the reduced worker number request. Currently unable to update this package due to OOM.
Please remove checks
Please do not, the checks run the tests which should be passing so we're not installing broken versions like the one that was released recently. If an individual user wants to skip the checks, they can do so easily enough (such as with the aforementioned --nocheck flag to paru).
Please do however change the number of workers to something small so it doesn't OOM/thrash swap.
Please remove checks. I don't think I can continue using this aur pkg anymore with the checks enabled.
I've hit some of the same others have issues listed here:
For me, the best temporary option was skipping the checks as Ralthius suggested, by adding --nocheck to the flags I passed to paru.
Two tests fail at the end of the build for me, so the package can not get created. The error is that the AWS region ap-southeast-1 does not match us-mars-2 (??)
Pinned Comments
kstolp commented on 2024-10-23 05:14 (UTC)
If you receive this error when trying to build, it is because you have not imported the GPG keys used for verification.
You have two options:
1) Import the key into your keyring. ArchWiki article. The key is available in this repo, which is copied from the AWS documentation. e.g.
gpg --import keys/pgp/FB5DB77FD5C118B80511ADA8A6310ACC4672475C.asc. (recommended)2) Alternatively, you can skip this verification by passing the
--skippgpcheckargument tomakepkgwhen building. (not recommended)