Package Details: google-cloud-cli-bundled-python3-unix 537.0.0-1

Git Clone URL: https://aur.archlinux.org/google-cloud-cli.git (read-only, click to copy)
Package Base: google-cloud-cli
Description: gcloud Bundled Python 3.12
Upstream URL: https://cloud.google.com/cli/
Keywords: cloud gcloud gcp google sdk
Licenses: Apache-2.0
Submitter: PolarianDev
Maintainer: jvybihal
Last Packager: jvybihal
Votes: 191
Popularity: 0.159193
First Submitted: 2023-03-08 09:33 (UTC)
Last Updated: 2025-09-03 17:43 (UTC)

Pinned Comments

jvybihal commented on 2025-06-30 06:37 (UTC)

I did a split of the package to 3 packages: google-cloud-cli, google-cloud-cli-bq, google-cloud-cli-gsutil. There is also package containing the bundled python for those who want it or as a dependency to the gsutil (current version 5.24 does not work with python 3.13 out-of-the-box, although 5.25 which is already available on github should). I am also testing to include other "components".

If there will be interest, it's also possible to split the manpages to another package. So for those who don't want them, the install time can get faster and size significantly smaller.

I have tried not to break anyones installation, so please try to install the 3 mentioned packages and it should work the same as before.

You don't need bundled python for the gcloud to work, and I would advice to use gsutil only if yo really have to. The prefered way is to use gcloud storage anyway.

Latest Comments

« First ‹ Previous 1 .. 26 27 28 29 30 31 32 33 34 Next › Last »

gideonite commented on 2015-08-23 16:43 (UTC)

@ac4r_g0 Running `gcloud alpha genomics variants` gives me the error: ERROR: (gcloud) The update action could not be performed because the installation root of the Cloud SDK could not be located. Please re-install the Cloud SDK and try again. I tried re-installing and re-authenticating but no dice.

gideonite commented on 2015-08-23 16:40 (UTC)

@troyengel Unfortunately, I think it will be difficult to properly create a bdutil package. The user is required to manually modify a script called `bdutil_env.sh` will Google specific project and bucketids. Since bdutil comes with a binary, it's probably not worth creating a package until this type of manual configuration is no longer required (if ever).

tengel commented on 2015-08-22 01:24 (UTC)

@gideeonite - you are correct, it's a separate download for some reason so you'd make a new package for it. In that PKGBUILD you'd set a requires() of this package to satisfy the install dependencies. https://storage.googleapis.com/hadoop-tools/bdutil/bdutil-latest.tar.gz

gideonite commented on 2015-08-21 19:54 (UTC)

From what I gather bdutil is not included in the Google Cloud SDK. Not sure what the reason for this is. Does it warrant creating a new package? More info here: https://cloud.google.com/hadoop/bdutil.

tengel commented on 2015-08-21 00:36 (UTC)

FYI: the 0.9.74 update has removed all the help/man files, which means all the man pages in 0.9.73 and before will disappear with this upgrade. There's no mention of this on their website or the RELEASE_NOTES, so I just commented out the PKGBUILD commands for now. It's possible this is a mistake when someone at Google made the new tarball as it seems rather odd - there are over 400 man pages in the older tarball.

lufalas commented on 2015-08-20 11:58 (UTC)

New release 0.9.74. 0.9.74 (2015/08/19) ================== - new list and import commands under `gcloud alpha genomics variants`.

tengel commented on 2015-08-14 01:07 (UTC)

@oryband - read all the other comments, it was a new release. You must look at RELEASE_NOTES to know if it's a new version of the tarball. I've updated the PKGBUILD.

oryband commented on 2015-08-12 08:21 (UTC)

still experiencing failed validity checks, please update for now i've been able to install with yaourt by using: yaourt --m-arg "--skipchecksums" google-cloud-sdk that skipchecksums is a makepkg argument that tells makepkg to ignore the checksum :)

tengel commented on 2015-07-31 12:42 (UTC)

@ogarcia - flagging the package out of date is good enough. Google uses the same download filename on their website, so new versions will of course produce bad checksums -- you have to look at the RELEASE_NOTES inside the tarball to see if it's a new version.