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 .. 5 6 7 8 9 10 11 12 13 14 15 .. 31 Next › Last »

sudoforge commented on 2022-09-18 04:26 (UTC)

@pintert3, if you're still experiencing that, the solution is to navigate to wherever paru stores the repository on your filesystem, and either delete it, or run the following:

$ git merge --abort   # this is a guess; try `git rebase --abort` if you aren't in a merge

$ git fetch origin

$ git reset --hard origin/master

taba commented on 2022-09-16 03:20 (UTC)

What the hell. I accidentally ran gcloud without firejail because I didn't notice that my PATH was being changed with export PATH=$CLOUDSDK_ROOT_DIR/bin:$PATH. Please make it so /usr/local/sbin:/usr/local/bin stays in the beginning. PATH="$PATH":"$CLOUDSDK_ROOT_DIR/bin" would be ideal.

pintert3 commented on 2022-09-14 14:38 (UTC)

Any solution to @yazgoo's problem? What I know for sure, it's definitely an issue with paru

jeanlucthumm commented on 2022-09-13 23:29 (UTC)

For fish users running into the problem @sudoforge mentioned, you can also use bass (https://github.com/edc/bass) to source the relevant file directly:

bass source /etc/profile.d/google-cloud-sdk.sh

yazgoo commented on 2022-08-11 13:46 (UTC) (edited on 2022-08-12 06:10 (UTC) by yazgoo)

Hi, I'm getting the following error when updating via paru:

error: command failed: .cache/paru/clone/google-cloud-sdk: git -c user.email=aur -c user.name=aur merge --no-edit --no-ff --no-commit

More precisely:

Auto-merging .SRCINFO
CONFLICT (content): Merge conflict in .SRCINFO
Auto-merging PKGBUILD
CONFLICT (content): Merge conflict in PKGBUILD
Automatic merge failed; fix conflicts and then commit the result.

Here is part of the diff

index f2d78b2,ede1bbe..0000000
--- a/.SRCINFO
+++ b/.SRCINFO
@@@ -1,6 -1,6 +1,10 @@@
  pkgbase = google-cloud-sdk
        pkgdesc = A set of command-line tools for the Google Cloud Platform. Includes gcloud (with beta and alpha commands), gsutil, and bq.
++<<<<<<< HEAD
 +      pkgver = 391.0.0
++=======
+       pkgver = 397.0.0
++>>>>>>> refs/remotes/origin/master

sudoforge commented on 2022-05-31 20:17 (UTC)

@Sam-Burgos, look at this random internet search result for more info: https://unix.stackexchange.com/questions/675521/make-systemd-service-inherit-environment-variables-from-etc-profile-d

sudoforge commented on 2022-05-31 20:14 (UTC)

@Sam-Burgos, see the pinned comment about this issue.

Based on your description of the issue you are experiencing, it sounds like these script you're executing do not inherit the CLOUDSDK_* environment variables. Running a script as a systemd unit, for example, will not inherit environment variables defined in /etc/profile or in a script under /etc/profile.d; you will need to specify these in your script's environment(s).

Santi-Burgos commented on 2022-05-31 17:42 (UTC)

Greetings, I have the issue with the library libcrypt.so.1 as well when trying to run the command as an automated bash file, however, my default shell is actually bash and it runs ok only if I run it manually. If I try to automate somehow (via bash, systemd timer or any other) it doesn't work

Is there any way to test what might be wrong or to report this?

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

385.0.0-2 works, thanks for update.

sudoforge commented on 2022-05-11 12:02 (UTC)

385.0.0-2 resolved the issue. If you are still experiencing a build failure, you are not building 385.0.0-2.