Package Details: aws-cli-v2 2.15.51-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
Conflicts: aws-cli
Provides: aws-cli
Submitter: jelly
Maintainer: kino_t
Last Packager: kino_t
Votes: 13
Popularity: 9.36
First Submitted: 2024-04-21 11:04 (UTC)
Last Updated: 2024-05-15 22:58 (UTC)

Required by (20)

Sources (13)

Pinned Comments

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

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

disabling checks in yay can be done like this

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

Latest Comments

1 2 3 4 5 Next › Last »

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

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.