Package Details: aws-cli-v2 2.25.6-1

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: 38
Popularity: 5.77
First Submitted: 2024-04-21 11:04 (UTC)
Last Updated: 2025-03-30 00:52 (UTC)

Required by (20)

Sources (9)

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.

==> ERROR: One or more PGP signatures could not be verified!

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 --skippgpcheck argument to makepkg when building. (not recommended)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

dreieck commented on 2024-06-23 10:57 (UTC)

The key FB5DB77FD5C118B80511ADA8A6310ACC4672475C in validpgpkeys is expired since 2023-09-17:

gpg --recv-keys FB5DB77FD5C118B80511ADA8A6310ACC4672475C && gpg --list-key FB5DB77FD5C118B80511ADA8A6310ACC4672475C: 

gpg: enabled compatibility flags:
gpg: data source: http://185.125.188.26:80
gpg: armor header: Comment: Hostname:
gpg: armor header: Version: Hockeypuck 2.2
gpg: pub  rsa4096/A6310ACC4672475C 2019-09-18  AWS CLI Team <aws-cli@amazon.com>
gpg: key A6310ACC4672475C: 3 signatures not checked due to missing keys
gpg: key A6310ACC4672475C: "AWS CLI Team <aws-cli@amazon.com>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
gpg: enabled compatibility flags:
gpg: using pgp trust model
pub   rsa4096 2019-09-18 [SC] [expired: 2023-09-17]
      FB5DB77FD5C118B80511ADA8A6310ACC4672475C
uid           [ expired] AWS CLI Team <aws-cli@amazon.com>

Regards!

cahva commented on 2024-06-07 14:12 (UTC)

Thank you for disabling the tests <3 I too was a little bit frustrated so I have skipped a couple of timesthe update when I knew that I did not have time to supervise the long install.

Anyway, thanks for maintaining this!

jerixmx commented on 2024-06-06 04:18 (UTC)

Was getting Starting build()... /home/xxxx/.pyenv/versions/3.11.9/bin/python: No module named build ==> ERROR: A failure occurred in build().

$ pyenv deactivate pyenv-virtualenv: no virtualenv has been activated.

Setting pyenv local system resolved it for me.

samthurston commented on 2024-05-28 13:34 (UTC)

If you have a virtual environment activated when installing aws-cli-v2 via yay, the build command tries to execute in the venv rather than using the system python.

josca commented on 2024-05-22 16:31 (UTC)

Please stop running the project's entire test suite while installing it! I'm not trying to develop on aws cli I'm just here to use the finished product!

samthurston commented on 2024-05-17 21:55 (UTC)

running 69k tests by default in an install is really, really abnormal behavior for an AUR package. Please disable the test suite by default. it's crazy that if i don't want to sit and watch it spin for 20 minutes I have to come here to find directions to disable the checks (which disables all the well-behaved checks of other packages as well)

n1ngu commented on 2024-05-17 09:16 (UTC)

If anyone runs into the error

AttributeError: 'ExternalAliasCommand' object has no attribute 'subcommand_table'

this is because for some (wrong?) reason the build is trying to generate autocompletion for your local cli aliases.

A workaround is to remove and restore your aliases while building.

mv ~/.aws/cli/alias ~/.aws/cli/.alias
# build!
mv ~/.aws/cli/.alias ~/.aws/cli/alias

I don't think it makes any sense to try to generate autocompletion for local aliases. This might be an upstream issue but this AUR package would really help being chrooted while being built!

rakatan commented on 2024-05-15 19:53 (UTC)

another way to fix tests is to set the timezone to UTC:

env TZ=UTC paru aws-cli-v2

mitch_feaster commented on 2024-05-15 19:30 (UTC) (edited on 2024-05-15 19:30 (UTC) by mitch_feaster)

No, users should not be responsible for running the test suite for every package they install on their system. They can if they want but it certainly shouldn't be the default.

The tests are run during development, integration, and release. Re-testing an already tested release on every install is a waste of time and compute resources.

GrzegorzKozub commented on 2024-05-14 05:28 (UTC)

For paru, use --nocheck to skip the check() function which contains the tests:

paru -S --aur --noconfirm --nocheck aws-cli-v2

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »