Package Details: google-cloud-sdk 259.0.0-1

Git Clone URL: https://aur.archlinux.org/google-cloud-sdk.git (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: https://cloud.google.com/sdk/
Keywords: cloud gcloud gcp google sdk
Licenses: Apache
Submitter: barnybug
Maintainer: sudoforge
Last Packager: sudoforge
Votes: 124
Popularity: 1.949251
First Submitted: 2014-06-03 08:10
Last Updated: 2019-08-20 18:41

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:

https://github.com/sudoforge/pkgbuilds/issues

sudoforge commented on 2018-08-21 22:09

IMPORTANT NOTE!

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 of the additional components for your day-to-day workflow, set "disable_updater": false in /opt/google-cloud-sdk/lib/googlecloudsdk/core/config.json and manage components using gcloud components <command>.

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

Latest Comments

1 2 3 4 5 6 ... Next › Last »

sudoforge commented on 2019-05-04 12:37

@Brinox:

I have confirmed this regression and updated the pinned comment.

Brinox commented on 2019-01-27 10:54

The described mechanism of installing additional components by modifying the _additional_components variable does not work. The SDK installer just won't install the given components, because "disable_updater" is set to true. This seems to affect the bootstrap install, too.

sudoforge commented on 2019-01-15 09:03

@esbdb and @oskar - There has been a pinned comment with instructions for managing components since August 2018.

oskar commented on 2019-01-15 08:42

I wasn't able to update kubectl component either due to the following error:

ERROR: (gcloud.components.remove) 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 described at: <https://cloud.google.com/sdk/>

I circumvented this by installing kubectl package from AUR (which is up-to-date) and removing /opt/google-cloud-sdk/bin/kubectl.

esbdb commented on 2018-10-30 06:56

How do I actually update installed components? I'm still running kubectl 1.7.2. Even when update gcloud, gcloud components update never gets run.

sudoforge commented on 2018-10-20 15:36

@mathieu.clabaut:

You can follow the very straightforward instructions in the pinned comment to add additional components. No additional components will be added to this PKGBUILD at any time now or in the future.

mathieu.clabaut commented on 2018-10-20 12:23

First, I must thank you for your useful package.

I'd like to ask if it Wouldn't be possible to keep the app engine component in this package until the other package is available ?

sudoforge commented on 2018-09-14 15:14

@tuxsavvy Upon reading the output you posted, that would seem to be an error from the bootstrap script itself - or rather, that yaml cannot be imported from ruamel. Something definitely got borked with your environment, as that's a bundled SDK dependency included in the tarball that this PKGBUILD downloads from Google.

sudoforge commented on 2018-09-10 15:11

To report issues or request features, please use:

https://github.com/sudoforge/pkgbuilds/issues

sudoforge commented on 2018-09-10 15:10

@tuxsavvy

Apart from git diff output as that returns nothing I figured you want me to compare the previous major commit

No, the intent was to make sure you didn't have a dirty working tree (changes from HEAD). I don't need to see the difference between two commits if you've not diverged from origin like you say...

You should try deleting the repository from disk and re-cloning it, and building from that. I don't use aurman, and don't know what it's trying to do under the hood, but I can tell you with absolute certainty that python-ruamel-yaml is not a build dependency.