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: 40
Popularity: 7.04
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

1 2 3 4 5 6 .. 8 Next › Last »

cahva commented on 2025-04-16 15:47 (UTC)

@fossdd and @elessard Thanks so much, downgrade worked nicely and I could get back to work! Aur comments section definately needs some 👍 emoji functionality :)

fossdd commented on 2025-04-16 09:21 (UTC)

same error when installing from scratch. i downgraded the python-prompt_toolkit from last version (3.0.51-1) to 3.0.50-1 and aws cli started working again

thats probably caused by https://gitlab.archlinux.org/archlinux/packaging/packages/python-prompt_toolkit/-/commit/1a951688796d7eb9b1e6fbcbe8211a44d8b535d1

Use test-env so importlib can find package metadata.

elessard commented on 2025-04-16 08:36 (UTC)

upgraded my system and aws cli raised an error importing prompt_toolkit package:

$ aws
Traceback (most recent call last):
File "/usr/lib/python3.13/importlib/metadata/__init__.py", line 407, in from_name
return next(iter(cls.discover(name=name)))
StopIteration

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/bin/aws", line 19, in <module>
import awscli.clidriver
File "/usr/lib/python3.13/site-packages/awscli/clidriver.py", line 52, in <module>
from awscli.autoprompt.core import AutoPromptDriver
File "/usr/lib/python3.13/site-packages/awscli/autoprompt/core.py", line 17, in <module>
from awscli.autoprompt.prompttoolkit import PromptToolkitPrompter
File "/usr/lib/python3.13/site-packages/awscli/autoprompt/prompttoolkit.py", line 18, in <module>
from prompt_toolkit.application import Application
File "/usr/lib/python3.13/site-packages/prompt_toolkit/__init__.py", line 32, in <module>
__version__ = metadata.version("prompt_toolkit")
File "/usr/lib/python3.13/importlib/metadata/__init__.py", line 987, in version
return distribution(distribution_name).version
~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.13/importlib/metadata/__init__.py", line 960, in distribution
return Distribution.from_name(distribution_name)
~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.13/importlib/metadata/__init__.py", line 409, in from_name
raise PackageNotFoundError(name)
importlib.metadata.PackageNotFoundError: No package metadata was found for prompt_toolkit

same error when installing from scratch. i downgraded the python-prompt_toolkit from last version (3.0.51-1) to 3.0.50-1 and aws cli started working again. Do you have any tips to fix this issue or this package need to be patched?

huiser commented on 2025-02-23 08:57 (UTC)

I had the same "No module named build" error. Turned out my shell was in a virtual environment for a Python project.

Malvineous commented on 2025-01-28 07:11 (UTC)

@wuint-adf My apologies, I didn't realise that was an issue! After doing a full upgrade everything seems to be in sync and I was able to build the package.

wunit-adf commented on 2025-01-13 07:37 (UTC)

@Malvineous Check if you have a partial upgrade situation that leads to Python not finding its libraries:

pacman -Q python python-build

Malvineous commented on 2025-01-13 06:51 (UTC)

Is there a missing dependency on this?

(1/9) installing python-awscrt
(2/9) installing python-ruamel.yaml.clib
(3/9) installing python-ruamel-yaml
(4/9) installing python-execnet
(5/9) installing python-pytest-xdist
(6/9) installing python-pyproject-hooks
(7/9) installing python-build
(8/9) installing python-flit-core
(9/9) installing python-installer
[...]
==> Making package: aws-cli-v2 2.22.33-1 (Mon 13 Jan 2025 16:44:04)
==> Starting build()...
/usr/bin/python: No module named build
==> ERROR: A failure occurred in build().

nairb774 commented on 2024-12-16 19:23 (UTC)

If you find the time to build the auto-complete index to be a really long time, you might consider giving https://github.com/aws/aws-cli/issues/8889 a vote.

kstolp commented on 2024-11-10 17:22 (UTC)

@Thiger,

   awscli-2.19.1.tar.gz ... cat: Schreibfehler: Datenübergabe unterbrochen (broken pipe)

Something failed here. Have you run out of disk space? Have you updated the key from the recently expired one?

Either way, I would recommend using the officially supported tools and building in a clean chroot first when running into an issue. This will help determine if the issue is with the aur helper that you are using (pamac).

1 2 3 4 5 6 .. 8 Next › Last »