Package Details: google-cloud-sdk 235.0.0-1

Git Clone URL: (read-only)
Package Base: google-cloud-sdk
Description: A set of command-line tools for the Google Cloud Platform. Includes gcloud (with beta and alpha commands), gsutil, and bq.
Upstream URL:
Keywords: cloud gcloud gcp google sdk
Licenses: Apache
Submitter: barnybug
Maintainer: sudoforge
Last Packager: sudoforge
Votes: 114
Popularity: 4.274117
First Submitted: 2014-06-03 08:10
Last Updated: 2019-02-21 12:44

Dependencies (2)

Required by (6)

Sources (2)

Pinned Comments

sudoforge commented on 2018-09-10 15:11

To report issues or request features, please use:

sudoforge commented on 2018-08-21 22:09


Commit e01da1e449882ad8e4fe590b01cd09624b58143a removes the appengine components from this package. These components, along with all of the others, will be made available as independent packages in the future.

If you need any appengine components for your day to day workflow, you have two options:

  • Clone the repository, add in the additional components to the _additional_components list; or
  • Set "disable_updater": false in /opt/google-cloud-sdk/lib/googlecloudsdk/core/config.json and manage components using gcloud components <command>. This is probably the sanest way to go about diverging from the released package until I publish the components as separate packages.

Be sure to install any dependencies for the additional components that you may need.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 ... Next › Last »

oyvindsk commented on 2018-04-23 09:21

If you try to install or update packages with 'gcloud components ..' you'll get a

"You cannot perform this action because this Cloud SDK installation is managed by an external package manager. Please consider using a separate installation of the Cloud SDK created through the default mechanism .." error.

I call bullshit on this :) You can "fix" it by setting: "disable_updater": false in /opt/google-cloud-sdk/lib/googlecloudsdk/core/config.json

Maybe consider setting this since it makes this package much more useful.

troyengel commented on 2018-04-05 00:04

@MaddyBoo - would be happy to help, however I don't use zsh so I started looking into this... and it's horribly complicated. I can't find any wiki (including Arch's), blog, or man pages which indicate how you install system wide completion files. Everything talks about "must be explicitly enabled from your shell", and refer to triggering it from ~/.zshrc and it's $FPATH. (even man zshcompsys(1) has no clue)

Can you provide another 3rd party package here in Arch which provides zsh completion files systemwide? I looked into the zsh package itself and zsh-completions package, they don't own a system directory (like /etc/zsh.completions.d/ or /etc/zsh/completions or whatnot), so it's just not clear what you do with this file ( provided. Guidance and instructions needed. :)

MaddyBoo commented on 2018-04-04 06:26

The PKGBUILD seems to install the bash completions but not the zsh completions, can we get this fixed?

oxplot commented on 2018-02-14 03:24

@troyengel optional subpackage seems to be the ideal thing to do, but I'm not familiar with it and it'll take me sometime to get around to it. Meanwhile, I'll try to get patches in if someone else can work on it.

troyengel commented on 2018-02-04 15:15

The inclusion of google-appengine-go in release 186.0.0 has more than doubled the size of this entire package to over 500MB, it appears that there's a lot of go source getting bundled. Perhaps that can be culled manually.

==== Packages (1) google-cloud-sdk-186.0.0-1

Total Installed Size: 562.75 MiB Net Upgrade Size: 359.64 MiB ====

That was rather unexpected, perhaps the go engine should be an optional subpackage.

adangert commented on 2018-02-01 06:10

File "/usr/lib/python2.7/", line 286, in match_hostname % (hostname, dnsnames[0])) ssl.CertificateError: hostname '' doesn't match ''

oxplot commented on 2017-11-09 22:54

@johnny12 you can safely ignore those warnings

johnny12 commented on 2017-11-09 13:01

A little over a week ago I installed google-cloud-sdk 177 from the AUR. Since then I upgraded twice to version 178 and now to 179. Both times I received the following warning:
WARNING: There are older versions of Google Cloud Platform tools on your system PATH.
Please remove the following to avoid accidentally invoking these old tools:


Is it desired to fix this warning and if so then how, by simply deleting the files mentioned there? Or should I just ignore this warning? The files listed are all the files in the bin/ directory. Apart from those files there is also a folder named "bootstrapping" that contains files that seem to be related to the files in the bin/ directory, should I also delete that folder (and thus empty the bin/ directory)?


oxplot commented on 2017-09-30 09:39

@The_K thanks for the patch. Merged now.

oxplot commented on 2017-09-30 09:21

@Nowaker done