The only exception to that I've encountered was OS X (not linux, but still). And the brew installed python adds it anyway.
Alternatively you can export CLOUDSDK_PYTHON=python2 and then gcloud/gsutil/bq/etc will use the right pythong without modifications. but it's a bit stupid that they don't just default to python2 and fallback to python.
Search Criteria
Package Details: google-cloud-cli 517.0.0-1
Package Actions
| 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: | 190 |
| Popularity: | 0.68 |
| First Submitted: | 2023-03-08 09:33 (UTC) |
| Last Updated: | 2025-04-02 08:09 (UTC) |
Dependencies (2)
- python (python37AUR, python311AUR, python310AUR)
- python-crcmod (optional) – [gsutil] verify the integrity of GCS object contents
Required by (14)
- arkade-bin (requires google-cloud-sdk) (optional)
- gcsfuse (requires google-cloud-sdk) (optional)
- gcsfuse-bin (requires google-cloud-sdk) (optional)
- google-cloud-cli-firestore-emulator
- google-cloud-cli-gke-gcloud-auth-plugin
- google-cloud-sdk-app-engine-java (requires google-cloud-sdk)
- google-cloud-sdk-app-engine-python (requires google-cloud-sdk)
- google-cloud-sdk-app-engine-python-extras (requires google-cloud-sdk)
- google-cloud-sdk-datastore-emulator (requires google-cloud-sdk)
- k3sup-bin (requires google-cloud-sdk) (optional)
- porter-bin (requires google-cloud-sdk) (optional)
- python-google-earthengine-api (requires google-cloud-sdk)
- repman (optional)
- repman-git (optional)
Sources (4)
justin8 commented on 2015-12-17 02:08 (UTC)
tengel commented on 2015-12-17 01:03 (UTC)
@tuxfusion - you've broken your python2 install. The symlink is created as part of the package:
https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/python2#n95
$ pacman -Qo /usr/bin/python2
/usr/bin/python2 is owned by python2 2.7.11-1
The use of a python2 link is used across all distributions (I had to do something for work that confirmed this - RHEL/CentOS 5, 6, 7, Debian, Ubuntu, etc.) so it's an expected configuration to be on almost every Linux out there besides Arch. (just FYI)
tuxfusion commented on 2015-12-16 15:18 (UTC)
I have the same python problem. /etc/profile.d/google-cloud-sdk.sh points to "python2" which doesn't exist on my system or the repo. Manually exporting "python2.7" instead works if it's installed. executing the .sh or restarting the terminal won't help here, I suppose.
tengel commented on 2015-12-13 13:58 (UTC)
@vendion - did you log out and back in (the terminal or desktop, depending on your setup) after installing it? That's Google's code, if the variable CLOUDSDK_PYTHON is null or doesn't equal python2 that strange logic of theirs is triggered. The AUR package adds /etc/profile.d/google-cloud-sdk.sh which is sourced when you log in to set up the basic envvars which set that var to python2.
vendion commented on 2015-12-13 03:15 (UTC)
Links against the wrong Python: /usr/bin/gcloud: line 119: python22: command not found
That should probably be python2 or python2.7
tengel commented on 2015-12-12 01:02 (UTC)
Quick note - Google changed the release numbering scheme with the release 90.0.0 that I just pushed up, see RELEASE_NOTES for details on the change.
tengel commented on 2015-11-07 17:06 (UTC)
@ogarcia - roger that, try now with the new 0.9.85-4 release. This was one of the new files in the new tarball we're using, I added a line to remove this symlink during build and leave it for google-appengine-python where it fits better.
ogarcia commented on 2015-11-07 16:51 (UTC)
This have conflicts with "google-appengine-python" cause /usr/bin/dev_appserver.py exist in both.
tengel commented on 2015-11-06 17:20 (UTC)
OK we should be all set -- the changes are very large to the PKGBUILD, so y'all report if anything is still broken (it took me 3 tries to fix the man page permissions, sorry). I've also added 'kubectl' component during build which isn't included in the core SDK tarball but seems safe and useful. I've also added the prepare() function that will try and alert that the upstream source has a newer release. :)
$ gcloud info
Google Cloud SDK [0.9.85]
Platform: [Linux, x86_64]
Python Version: [2.7.10 (default, Sep 7 2015, 13:51:49) [GCC 5.2.0]]
Site Packages: [Disabled]
Installation Root: [/opt/google-cloud-sdk]
Installed Components:
core: [2015.10.30]
core-nix: [2015.10.30]
kubectl: []
app: [2015.10.30]
gcloud: [2015.10.30]
gsutil-nix: [4.15]
gsutil: [4.15]
bq: [2.0.18]
kubectl-linux-x86_64: [1.0.6]
bq-nix: [2.0.18]
...
tengel commented on 2015-11-06 15:35 (UTC)
I've also figured out what's wrong with our package for the "SDK_ROOT" that's causing the errors; the python code (lib/googlecloudsdk/core/config.py) is looking for a $CLOUDSDK_ROOT_DIR/.install/ subdirectory with the manifests and JSON files, which are in the tarball with a version -- I'm going to copy this .install over to the root in PKGBUILD, it seems to fix that whole issue when I do it manually.
Pinned Comments