Arch Linux User Repository

I did a split of the package to 3 packages: google-cloud-cli, google-cloud-cli-bq, google-cloud-cli-gsutil. There is also package containing the bundled python for those who want it or as a dependency to the gsutil (current version 5.24 does not work with python 3.13 out-of-the-box, although 5.25 which is already available on github should). I am also testing to include other "components".

If there will be interest, it's also possible to split the manpages to another package. So for those who don't want them, the install time can get faster and size significantly smaller.

I have tried not to break anyones installation, so please try to install the 3 mentioned packages and it should work the same as before.

You don't need bundled python for the gcloud to work, and I would advice to use gsutil only if yo really have to. The prefered way is to use gcloud storage anyway.

@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'

@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

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

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

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

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.

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.

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

update, please.

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