Package Details: google-cloud-cli 504.0.1-1

Git Clone URL: https://aur.archlinux.org/google-cloud-cli.git (read-only, click to copy)
Package Base: google-cloud-cli
Description: A set of command-line tools for the Google Cloud Platform. Includes gcloud (with beta and alpha commands), gsutil, and bq.
Upstream URL: https://cloud.google.com/cli/
Keywords: cloud gcloud gcp google sdk
Licenses: Apache-2.0
Conflicts: google-cloud-sdk
Provides: google-cloud-sdk
Replaces: google-cloud-sdk
Submitter: PolarianDev
Maintainer: jvybihal
Last Packager: jvybihal
Votes: 188
Popularity: 0.152152
First Submitted: 2023-03-08 09:33 (UTC)
Last Updated: 2024-12-23 07:29 (UTC)

Dependencies (2)

Required by (15)

Sources (3)

Pinned Comments

Latest Comments

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 31 Next › Last »

Showfom commented on 2022-05-11 12:01 (UTC)

Same error here for the latest version:

==> Starting prepare()...
failed to apply patch: 0004-collections-abc.patch
==> ERROR: A failure occurred in prepare().
    Aborting...
 -> error making: google-cloud-sdk

quest commented on 2022-05-11 09:39 (UTC)

Latest version fails to apply the collections patch.

failed to apply patch: 0004-collections-abc.patch
==> ERROR: A failure occurred in prepare().

sudoforge commented on 2022-04-25 02:14 (UTC) (edited on 2022-04-25 03:08 (UTC) by sudoforge)

There has been a recent influx of users reporting that they are encountering an error related to missing libcrypt.so.1:

error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory

If you encounter this error, the issue is that your shell has not imported /etc/profile.d/google-cloud-sdk.sh, causing the CLOUDSDK_PYTHON environment variable (among others) to not be set. This causes the tool to use a bundled python executable with its own library searching logic which fails to find the correct library.

libcrypt is provided by core/libxcrypt, which is required by core/python, which is required by aur/google-cloud-sdk. If you've installed this package, you have the correct library.

This is not a bug with the package; it is a bug with your shell. At the moment, this appears to be limited to users of fish. Please check the wiki for information about the tasks you should perform when setting fish as your default shell to avoid errors like this.

sudoforge commented on 2022-03-23 16:22 (UTC)

Note: I overhauled my internal CI process that updates packages and syncs them out to external destinations (like the AUR). Please open an issue using the issue tracker if you encounter any issues.

cameronraysmith commented on 2022-02-25 16:19 (UTC)

@sudoforge @ginjiruu I received the same error in bash and fixed by installing https://archlinux.org/packages/core/x86_64/libxcrypt-compat/ as described here https://bbs.archlinux.org/viewtopic.php?pid=2022246#p2022246 (but now in community rather than aur) due to dropping libcrypt.so.1 from glibc.

mccurdyc commented on 2022-02-20 12:17 (UTC)

@sudoforge export CLOUDSDK_PYTHON=$(which python3) also fixed it for me on zsh. Thanks!

sudoforge commented on 2022-02-15 21:55 (UTC)

To those curious: ginjiruu was using fish, which apparently doesn't source /etc/profile, causing the CLOUDSDK_PYTHON variable to be unset (among other important variables). Specifically, when CLOUDSDK_PYTHON is unset, gcloud uses a vendored python3 executable, which wasn't linked appropriately.

I will likely remove this bundled python in future releases.

sudoforge commented on 2022-02-15 16:32 (UTC)

@ginjiruu Please open an issue using the issue tracker, and I'll follow up with you today to debug this issue specific to your environments.

ginjiruu commented on 2022-02-15 16:07 (UTC)

@sudoforge I don't believe so. Was able to build version 371 just fine with the same shell config. First system tried was a local arch installation and the other was a wsl2 install that also succeeded on version 371 and is also having issues now

sudoforge commented on 2022-02-15 15:54 (UTC) (edited on 2022-02-15 16:03 (UTC) by sudoforge)

@ginjiruu This does not occur in a clean chroot, nor on my local system (outside of a chroot). Are you building this in a python virtual environment, or do you otherwise have a python virtual environment active in the shell session you are attempting to build it in?

Edit: And to be clear, you are encountering this error when building the package on your systems (as opposed to encountering it when running commands), correct?

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 31 Next › Last »