Arch Linux User Repository

error in building script after today's update

Installing bash completion script Fixing python references for python2 and compiling *.pyc Compiling /home/pio/.cache/yay/google-cloud-sdk/pkg/google-cloud-sdk/opt/google-cloud-sdk/lib/googlecloudsdk/api_lib/dns/active_peering_zones.py ... SyntaxError: future feature google_type_annotations is not defined (active_peering_zones.py, line 19)

Not building after today's system update:

Installing bash completion script Fixing python references for python2 and compiling *.pyc Compiling /home/ewaller/devel/build/google-cloud-sdk/pkg/google-cloud-sdk/opt/google-cloud-sdk/lib/googlecloudsdk/api_lib/dns/active_peering_zones.py ... SyntaxError: future feature google_type_annotations is not defined (active_peering_zones.py, line 19)

==> ERROR: A failure occurred in package().

@chibby0ne, this is very likely an upstream issue, but I've filed it and will be following up on Github:

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

I've read the pinned comment from @sudoforge, and the comments from @oskar and @esbdb, but these assume that kubectl is installed.

I've just installed this package which is now in version 270.0.0-3, and it looks like it doesn't bring kubectl anymore but it still shows up as installed in the output of gcloud components list:

Your current Cloud SDK version is: 270.0.0
The latest available version is: 270.0.0

+------------------------------------------------------------------------------------------------------------+
|                                                 Components                                                 |
+---------------+------------------------------------------------------+--------------------------+----------+
|     Status    |                         Name                         |            ID            |   Size   |
+---------------+------------------------------------------------------+--------------------------+----------+
| Not Installed | App Engine Go Extensions                             | app-engine-go            |  4.9 MiB |
| Not Installed | Cloud Bigtable Command Line Tool                     | cbt                      |  7.5 MiB |
| Not Installed | Cloud Bigtable Emulator                              | bigtable                 |  6.6 MiB |
| Not Installed | Cloud Datalab Command Line Tool                      | datalab                  |  < 1 MiB |
| Not Installed | Cloud Datastore Emulator                             | cloud-datastore-emulator | 18.4 MiB |
| Not Installed | Cloud Firestore Emulator                             | cloud-firestore-emulator | 40.0 MiB |
| Not Installed | Cloud Pub/Sub Emulator                               | pubsub-emulator          | 34.9 MiB |
| Not Installed | Cloud SQL Proxy                                      | cloud_sql_proxy          |  3.8 MiB |
| Not Installed | Emulator Reverse Proxy                               | emulator-reverse-proxy   | 14.5 MiB |
| Not Installed | Google Cloud Build Local Builder                     | cloud-build-local        |  6.0 MiB |
| Not Installed | Google Container Registry's Docker credential helper | docker-credential-gcr    |  1.8 MiB |
| Not Installed | Skaffold                                             | skaffold                 | 22.1 MiB |
| Not Installed | gcloud app Java Extensions                           | app-engine-java          | 85.9 MiB |
| Not Installed | gcloud app PHP Extensions                            | app-engine-php           |          |
| Not Installed | gcloud app Python Extensions                         | app-engine-python        |  6.0 MiB |
| Not Installed | gcloud app Python Extensions (Extra Libraries)       | app-engine-python-extras | 27.1 MiB |
| Installed     | BigQuery Command Line Tool                           | bq                       |  < 1 MiB |
| Installed     | Cloud SDK Core Libraries                             | core                     | 12.3 MiB |
| Installed     | Cloud Storage Command Line Tool                      | gsutil                   |  3.6 MiB |
| Installed     | gcloud Alpha Commands                                | alpha                    |  < 1 MiB |
| Installed     | gcloud Beta Commands                                 | beta                     |  < 1 MiB |
| Installed     | kubectl                                              | kubectl                  |  < 1 MiB |
+---------------+------------------------------------------------------+--------------------------+----------+
To install or remove components at your current SDK version [270.0.0], run:
  $ gcloud components install COMPONENT_ID
  $ gcloud components remove COMPONENT_ID

To update your SDK installation to the latest version [270.0.0], run:
  $ gcloud components update

@bswartz thanks for catching that; python3 should have been an optdep.

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:

• Your workflow will break if my commits are no longer signed with my PGP key, or
• Your workflow will break if the package owner changes

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