Arch Linux User Repository

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.

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.

@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.

This have conflicts with "google-appengine-python" cause /usr/bin/dev_appserver.py exist in both.

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] ...

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.

Heya guys, UI have the morning off and I'm figuring something out -- I found the openSUSE Factory RPM SPEC file which provided a critical clue, this magic file: https://dl.google.com/dl/cloudsdk/release/sha1.txt ...and sure enough, we can download numbered releases (including the older ones, they're in the downloads/ subdirectory if you wget them by hand). The file downloads/google-cloud-sdk-0.9.85-linux-x86_64.tar.gz has a layout slightly different (with more things too) than the one we're using, but this is good -- it contains the man pages again! Here's a quick diff from the basic download and the numbered one above: $ diff -qr google-cloud-sdk.1 google-cloud-sdk.2 Only in google-cloud-sdk.2/.install: app.manifest Only in google-cloud-sdk.2/.install: app.snapshot.json Only in google-cloud-sdk.2/.install: bq-nix.manifest Only in google-cloud-sdk.2/.install: bq-nix.snapshot.json Only in google-cloud-sdk.2/.install: bq.manifest Only in google-cloud-sdk.2/.install: bq.snapshot.json Only in google-cloud-sdk.2/.install: core-nix.manifest Only in google-cloud-sdk.2/.install: core-nix.snapshot.json Only in google-cloud-sdk.2/.install: gcloud.manifest Only in google-cloud-sdk.2/.install: gcloud.snapshot.json Only in google-cloud-sdk.2/.install: gsutil-nix.manifest Only in google-cloud-sdk.2/.install: gsutil-nix.snapshot.json Only in google-cloud-sdk.2/.install: gsutil.manifest Only in google-cloud-sdk.2/.install: gsutil.snapshot.json Files google-cloud-sdk.1/bin/bootstrapping/.default_components and google-cloud-sdk.2/bin/bootstrapping/.default_components differ Only in google-cloud-sdk.2/bin/bootstrapping: bq.py Only in google-cloud-sdk.2/bin/bootstrapping: gsutil.py Only in google-cloud-sdk.2/bin: bq Only in google-cloud-sdk.2/bin: dev_appserver.py Only in google-cloud-sdk.2/bin: gcloud Only in google-cloud-sdk.2/bin: git-credential-gcloud.sh Only in google-cloud-sdk.2/bin: gsutil Only in google-cloud-sdk.2: help Only in google-cloud-sdk.2/lib/googlecloudsdk: appengine Only in google-cloud-sdk.2/lib/googlecloudsdk: compute Only in google-cloud-sdk.2: platform Only in google-cloud-sdk.2: properties So we can sort this out now, I'm just working through the differences and trying to sort out a sane, logical way to make sure we don't break anything moving over to the other file. I was thinking of even adding a wget of the file above and alerting "new version detected, alert AUR maintainer!" during the build cycle or something...

You can set the hash to 'SKIP' and it won't be checked. but it really should be google who are rather terrible at not updating versioned packages of this tool.

Isn't there a way to bypass the md5 validity check from failing everyone update? this happens too often

I'm getting this as well while running `gcloud components update app`: > 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. Double checked, and `CLOUDSDK_ROOT_DIR` evaluates to '/opt/google-cloud-sdk' and '/opt/google-cloud-sdk/bin' is in my PATH.

0.9.80 is latest, md5sum f8a2fabb13e9bd02c7f8b34eb7a4c908