| 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.55 |
| First Submitted: | 2023-03-08 09:33 (UTC) |
| Last Updated: | 2025-04-16 16:59 (UTC) |
This package no longer builds. The error message is:
==> Starting package()...
Copying core SDK components
Running bootstrapping script
/home/arch/google-cloud-sdk/PKGBUILD: line 38: python2: command not found
==> ERROR: A failure occurred in package().
Aborting...
Hey folks,
The PKGBUILD has been updated from 261.0.0 to 263.0.0. I apologize for skipping 262.0.0's release; I was out of town.
I'm in the process of working out how I want to automate these updates, since Google is a trusted source (at least in terms of package integrity). I currently use a mashed up shell script to do this for me, but it still needs to be manually invoked -- after it's completion, I create the commit and handle pushing to Github (the source of truth for the PKGBUILD) and then subtree the google-cloud-sdk directory out to the AUR.
I'll almost certainly have to do two things:
1) Stop signing the Git commits with my PGP key
2) Use a passwordless key to push to the AUR
1 is more or less unimportant, as I doubt anyone has workflows that rely on my key. 2 is more concerning, as it would mean that the machine I'm using to update the AUR package is able to hit the git server with a passwordless RSA key. To limit the attack vector to packages which have a "trusted upstream source" (like this one), I'll be adding a bot user as a co-maintainer. I may eventually remove my personal account from this package if this proves successful.
Let me know if:
@Brinox:
I have confirmed this regression and updated the pinned comment.
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.
@esbdb and @oskar - There has been a pinned comment with instructions for managing components since August 2018.
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.
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.
@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.
Pinned Comments