Package Details: aws-cli-v2 2.22.2-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: 28
Popularity: 4.31
First Submitted: 2024-04-21 11:04 (UTC)
Last Updated: 2024-11-21 03:58 (UTC)

Required by (19)

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 Next › Last »

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

ei-grad commented on 2024-05-13 07:24 (UTC) (edited on 2024-05-13 07:25 (UTC) by ei-grad)

Solved by !check in makepkg.conf

This should be mentioned in a pinned comment.

a2sc commented on 2024-05-06 13:30 (UTC)

in respect to https://docs.aws.amazon.com/cli/latest/userguide/getting-started-version.html , the key A6310ACC4672475C has to be added with gpg

ksuhiyp commented on 2024-05-06 11:19 (UTC)

disabling checks in yay can be done like this

yay -S package-name --mflags "--nocheck"

debendraoli commented on 2024-05-03 03:55 (UTC) (edited on 2024-05-03 03:58 (UTC) by debendraoli)

I never get to install this pkg due to test failures.

So frustrated, I'm going to release bin version of this pkg.

--nocheck is not supported on yay.

alexdandrea commented on 2024-05-02 08:04 (UTC) (edited on 2024-05-02 12:54 (UTC) by alexdandrea)

These tests are there for the developers of aws-cli to ensure features built are actually working and no regressions are introduced from version to version; they're not really meant as target platform integration tests.

So, when a test failure would occur, there wouldn't be a new release since that would've been caught on upstream side already. As such you could argue it is not really necessary to run them on package build.

However, the package does patch quite some stuff, so after all it is justified a bit. It seems, though, that these tests do pick up the environment and user-specific configuration that exists in the context where these tests are run. For the package it means it uses all env vars and $HOME/.aws/{credentials,config} and that really is a problem since many of us might have real credentials there...

These tests should have some kind of jail and a separate user where they're run (eg. for me the test suite finally breaks with an assertion that 'eu-central-1' != 'us-mars-2' - where eu-central-1 is the region configured in my $HOME/.aws/credentials).

PS: Thank you for providing this package!

UPDATE: Found out that you can build packages in a chroot, with paru's --chroot option and this solves everything. I will enable this option in /etc/paru.conf for all the builds.

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