Package Details: google-cloud-sdk 235.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: 114
Popularity: 4.288532
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:

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 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 ... Next › Last »

allgaeuer.fabian commented on 2018-09-04 07:12

@sudoforge Yes, the package has never bundled the app-engine-java component (I always installed the component by modifying the PKGBUILD file). I just wanted to highlight that installing a JDK or JRE is (and never was) sufficient to use the Java environment. This was a bug in the old package because it simply listed as an optional dependency:

'java-environment: for Java version of App Engine'

sudoforge commented on 2018-08-31 16:28

@tuxsavvy python2-ruamel-yaml is a (bundled) dependency of the SDK, and is not required for building. I'm not sure why you're experiencing that error.

Please upload the following to ptpbw.pw (or a similar pastebin service):

  • The current commit that your cloned repo is at (git rev-parse HEAD)
  • The output of git diff in your cloned repo
  • The output of makepkg -s

tuxsavvy commented on 2018-08-31 10:15

I believe python2-ruamel-yaml might be required because it would fail to complete otherwise. Here is my build log without the dependency:

==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found google-cloud-sdk_214.0.0.orig.tar.gz
  -> Found google-cloud-sdk.sh
==> Validating source files with sha256sums...
    google-cloud-sdk_214.0.0.orig.tar.gz ... Passed
    google-cloud-sdk.sh ... Passed
==> Extracting sources...
  -> Extracting google-cloud-sdk_214.0.0.orig.tar.gz with bsdtar
==> Starting prepare()...
  -> Checking for newer upstream release
  -> This AUR release: 214.0.0
  -> Latest upstream release: 214.0.0
==> Removing existing $pkgdir/ directory...
==> Entering fakeroot environment...
==> Starting package()...
  -> Copying core SDK components
  -> Running bootstrapping script and adding additional components
Traceback (most recent call last):
  File "/home/user/.cache/aurman/google-cloud-sdk/pkg/google-cloud-sdk/opt/google-cloud-sdk/bin/bootstrapping/install.py", line 12, in <module>
    import bootstrapping
  File "/home/user/.cache/aurman/google-cloud-sdk/pkg/google-cloud-sdk/opt/google-cloud-sdk/bin/bootstrapping/bootstrapping.py", line 46, in <module>
    from googlecloudsdk.core.updater import update_manager
  File "/home/user/.cache/aurman/google-cloud-sdk/pkg/google-cloud-sdk/opt/google-cloud-sdk/lib/googlecloudsdk/core/updater/update_manager.py", line 35, in <module>
    from googlecloudsdk.core import yaml
  File "/home/user/.cache/aurman/google-cloud-sdk/pkg/google-cloud-sdk/opt/google-cloud-sdk/lib/googlecloudsdk/core/yaml.py", line 32, in <module>
    from ruamel import yaml
ImportError: cannot import name yaml
==> ERROR: A failure occurred in package().
    Aborting...

sudoforge commented on 2018-08-29 03:47

@allgaeuer.fabian This package has, as of my maintership, never bundled the app-engine-java component. You should read and follow the instructions in the currently pinned comment.

allgaeuer.fabian commented on 2018-08-23 09:48

@sudoforge Regarding your commit e01da1e449882ad8e4fe590b01cd09624b58143a: the Java environment requires installation of an additional component app-engine-java. Installing just the JDK or JRE is not sufficient.

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

troyengel commented on 2018-07-13 23:20

I've gone ahead and pushed the update - as @sudoforge mentions, please use the link in the upper right "Flag package out-of-date" for AUR packages.

sudoforge commented on 2018-07-13 17:14

@deace Flagging a package as out-of-date is the proper way to inform the author of an update.

deace commented on 2018-07-13 10:00

update, please.

troyengel commented on 2018-06-16 18:01

The newest pacman exposed that the use of python2 -m compileall embeds the source directory of the packaging process into the resulting *.pyc files as strings. I've added a -d /opt/google-cloud-sdk to the compileall PKGBUILD step for this new 205.0.0 release and it seems to do the trick (checked it with strings), please holler if this breaks something though. I tested a quick gcloud and gsutil and they're functional. Ref: https://docs.python.org/2/library/compileall.html