@troyengel I will try your 138.0.0 version. (I just `gcloud components update' from 137.0.1 to 138.0.0.)
Search Criteria
Package Details: google-cloud-cli 518.0.0-1
Package Actions
| 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.57 |
| First Submitted: | 2023-03-08 09:33 (UTC) |
| Last Updated: | 2025-04-16 16:59 (UTC) |
Dependencies (2)
- python (python37AUR, python311AUR, python310AUR)
- python-crcmod (optional) – [gsutil] verify the integrity of GCS object contents
Required by (15)
- apollo-neo-env-manager-dev (optional)
- arkade-bin (requires google-cloud-sdk) (optional)
- gcsfuse (requires google-cloud-sdk) (optional)
- gcsfuse-bin (requires google-cloud-sdk) (optional)
- google-cloud-cli-firestore-emulator
- google-cloud-cli-gke-gcloud-auth-plugin
- google-cloud-sdk-app-engine-java (requires google-cloud-sdk)
- google-cloud-sdk-app-engine-python (requires google-cloud-sdk)
- google-cloud-sdk-app-engine-python-extras (requires google-cloud-sdk)
- google-cloud-sdk-datastore-emulator (requires google-cloud-sdk)
- k3sup-bin (requires google-cloud-sdk) (optional)
- porter-bin (requires google-cloud-sdk) (optional)
- python-google-earthengine-api (requires google-cloud-sdk)
- repman (optional)
- repman-git (optional)
Sources (4)
vgivanovic commented on 2016-12-19 04:17 (UTC)
tengel commented on 2016-12-18 17:33 (UTC)
@vgivanovic - looks like Google deleted the actual archives upstream for 137.0.1, they've released an updated 138.0.0 that builds. I just uploaded a fresh PKGBUILD for it, resync and try again - thanks for reporting.
vgivanovic commented on 2016-12-18 17:26 (UTC) (edited on 2016-12-19 04:13 (UTC) by vgivanovic)
ERROR: The component listing for Cloud SDK version [137.0.1] could not be found. Make sure this is a valid archived Cloud SDK version.
ERROR: (gcloud.components.install) Failed to fetch component listing from server. Check your network settings and try again.
This error started with 137.0.0. I am using `fish' if that makes a difference. Installation by hand works. I just did `gcloud components update' successfully.
rdoursenaud commented on 2016-11-16 06:54 (UTC)
@troyengel Thanks! I've been using your package for Google App Engine developments for a while now and it's working perfectly.
tengel commented on 2016-10-16 14:55 (UTC) (edited on 2016-10-16 14:57 (UTC) by tengel)
130.0.0 integrates all the below, quick link of changes: https://aur.archlinux.org/cgit/aur.git/commit/?h=google-cloud-sdk&id=edf70e9b24eff06ff59b93bbe9410fe9a43cb513
edit: just noticed I misspelled 'due' in one of my comments, will fix next release
tengel commented on 2016-10-11 14:08 (UTC)
@rdoursenaud - this seems workable, since I don't live this SDK code can you expand upon what "add the app-engine-python component" entails? is it similar to how we're bootstrapping the kubectl component? ( https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=google-cloud-sdk#n54 )
Adding the replaces/obsoletes and /usr/bin/ links is a no-brainer, just delete the lines in the PKGBUILD that are actually deleting them I put there because of our conflicts in the first place. :)
rdoursenaud commented on 2016-10-10 14:51 (UTC)
Hi @troyengel, maintainer of google-appengine-python-php here.
Looking at https://cloud.google.com/appengine/docs/php/download and https://cloud.google.com/appengine/docs/python/download it seems that the Google Cloud SDK is now superseding the Google App Engine SDK.
I thus plan on dropping the package.
To ensure a smooth transition, your package must provide the appengine related tools.
Could you please add a replaces=('google-appengine-python-php' 'google-appengine-
python' 'google-appengine-php'), install '/usr/bin/dev_appserver.py' and '/usr/bin/endpointscfg.py and add the app-engine-python component?
Or should we try another approach to provide component level packages, maybe?
tengel commented on 2016-10-08 18:21 (UTC)
I don't see any harm in this and it's trivial because we're already installing a profile.sh - there's very little google-fu hits when you look for GOOGLE_CLOUD_SDK_HOME so I think it's just something people started doing. I'll put in on my checklist for the next release (130.0.0).
velovix commented on 2016-10-08 01:28 (UTC)
It would be very helpful if this package set the GOOGLE_CLOUD_SDK_HOME environment variable or did something else to allow App Engine plugins to detect where the Cloud SDK home is. The Gradle plugin, for example, is unable to find the SDK on its own.
Here is the mechanism plugins use to find the SDK: https://github.com/GoogleCloudPlatform/appengine-plugins-core/blob/75255413b2f92ebe841238241ff40014bc2be0e3/src/main/java/com/google/cloud/tools/appengine/cloudsdk/PathResolver.java#L35
tengel commented on 2016-09-07 14:54 (UTC)
I will add a conflict once I get back to my build machine -- what that other package is doing is their concern, I am *intentionally* adding kubectl during the build process to this SDK package to avoid having yet another package for no reason, this utility belongs with this SDK.
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=google-cloud-sdk#n53
This package has been around a lot longer than the kubectl-bin, those packagers should be advised to also set a reverse conflict with google-cloud-sdk.
Pinned Comments