conda-forge / googleapis-common-protos-feedstock

A conda-smithy repository for googleapis-common-protos.

About googleapis-common-protos-feedstock-feedstock

Feedstock license: BSD-3-Clause

About googleapis-common-protos-feedstock

Home: https://github.com/googleapis/python-api-common-protos

Package license: Apache-2.0

Summary: Common protobufs used in Google APIs

Development: https://github.com/googleapis/python-api-common-protos

Documentation: https://github.com/googleapis/python-api-common-protos/blob/main/README.md

Google APIs common protos

googleapis-common-protos contains the python classes generated from the common protos in the https://github.com/googleapis/api-common-protos repository.

About googleapis-common-protos

Home: https://github.com/googleapis/python-api-common-protos

Package license: Apache-2.0

Summary: Common protobufs used in Google APIs

Development: https://github.com/googleapis/python-api-common-protos

Documentation: https://github.com/googleapis/python-api-common-protos/blob/main/README.md

Google APIs common protos

googleapis-common-protos contains the python classes generated from the common protos in the https://github.com/googleapis/api-common-protos repository.

About googleapis-common-protos-grpc

Home: https://github.com/googleapis/python-api-common-protos

Package license: Apache-2.0

Summary: Common protobufs used in Google APIs

Development: https://github.com/googleapis/python-api-common-protos

Documentation: https://github.com/googleapis/python-api-common-protos/blob/main/README.md

Google APIs common protos

googleapis-common-protos contains the python classes generated from the common protos in the https://github.com/googleapis/api-common-protos repository.

Current build status

All platforms:

Current release info

Name	Downloads	Version	Platforms

Installing googleapis-common-protos-feedstock

Installing googleapis-common-protos-feedstock from the conda-forge channel can be achieved by adding conda-forge to your channels with:

conda config --add channels conda-forge
conda config --set channel_priority strict

Once the conda-forge channel has been enabled, googleapis-common-protos, googleapis-common-protos-grpc can be installed with conda:

conda install googleapis-common-protos googleapis-common-protos-grpc

or with mamba:

mamba install googleapis-common-protos googleapis-common-protos-grpc

It is possible to list all of the versions of googleapis-common-protos available on your platform with conda:

conda search googleapis-common-protos --channel conda-forge

or with mamba:

mamba search googleapis-common-protos --channel conda-forge

Alternatively, mamba repoquery may provide more information:

# Search all versions available on your platform:
mamba repoquery search googleapis-common-protos --channel conda-forge

# List packages depending on `googleapis-common-protos`:
mamba repoquery whoneeds googleapis-common-protos --channel conda-forge

# List dependencies of `googleapis-common-protos`:
mamba repoquery depends googleapis-common-protos --channel conda-forge

About conda-forge

conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.

A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by Azure, GitHub, CircleCI, AppVeyor, Drone, and TravisCI it is possible to build and upload installable packages to the conda-forge anaconda.org channel for Linux, Windows and OSX respectively.

To manage the continuous integration and simplify feedstock maintenance conda-smithy has been developed. Using the conda-forge.yml within this repository, it is possible to re-render all of this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender.

For more information please check the conda-forge documentation.

Terminology

feedstock - the conda recipe (raw material), supporting scripts and CI configuration.

conda-smithy - the tool which helps orchestrate the feedstock. Its primary use is in the construction of the CI .yml files and simplify the management of many feedstocks.

conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)

Updating googleapis-common-protos-feedstock-feedstock

If you would like to improve the googleapis-common-protos-feedstock recipe or build a new package version, please fork this repository and submit a PR. Upon submission, your changes will be run on the appropriate platforms to give the reviewer an opportunity to confirm that the changes result in a successful build. Once merged, the recipe will be re-built and uploaded automatically to the conda-forge channel, whereupon the built conda packages will be available for everybody to install and use from the conda-forge channel. Note that all branches in the conda-forge/googleapis-common-protos-feedstock-feedstock are immediately built and any created packages are uploaded, so PRs should be based on branches in forks and branches in the main repository should only be used to build distinct package versions.

In order to produce a uniquely identifiable distribution:

• If the version of a package is not being increased, please add or increase the build/number.
• If the version of a package is being increased, please remember to return the build/number back to 0.

Feedstock Maintainers

• @BrentDorsey
• @leahecole
• @parthea
• @tswast
• @xylar

googleapis-common-protos-feedstock's Issues

@conda-forge-admin, please add bot automerge

Solution to issue cannot be found in the documentation.

• I checked the documentation.

Issue

n/a

Installed packages

n/a

Environment info

n/a

ClobberWarnings vs protobuf

Solution to issue cannot be found in the documentation.

• I checked the documentation.

Issue

It appears this package vendors a lot of content also included in the base protobuf package, which results in a huge number of ClobberWarnings (log):

ClobberWarning: This transaction has incompatible packages due to a shared path.
  packages: conda-forge/linux-64::protobuf-3.20.2-py310hd8f1fbe_1, conda-forge/noarch::googleapis-common-protos-1.57.0-pyhd8ed1ab_1
  path: 'lib/python3.10/site-packages/google/protobuf/__init__.py'

and different at-rest versions of protobuf as found by pip check (log):

+ pip check
dagster 1.1.3 has requirement protobuf<4,>=3.13.0, but you have protobuf 4.21.9.

Installed packages

The following NEW packages will be INSTALLED:

    _libgcc_mutex:                      0.1-conda_forge             conda-forge
    _openmp_mutex:                      4.5-2_gnu                   conda-forge
    aiohttp:                            3.8.3-py310h5764c6d_1       conda-forge
    aiosignal:                          1.3.1-pyhd8ed1ab_0          conda-forge
    alembic:                            1.8.1-pyhd8ed1ab_0          conda-forge
    arrow-cpp:                          8.0.1-py310h4f1c134_2_cpu   conda-forge
    async-timeout:                      4.0.2-pyhd8ed1ab_0          conda-forge
    zipp:                               3.11.0-pyhd8ed1ab_0         conda-forge
    zlib:                               1.2.13-h166bdaf_4           conda-forge
    zstd:                               1.5.2-h6239696_4            conda-forge

Environment info

show_channel_urls: True
conda_build:
  pkg_format: 2
  zstd_compression_level: 16

==> /home/conda/.condarc <==
pkgs_dirs:
  - /home/conda/feedstock_root/build_artifacts/pkg_cache
  - /opt/conda/pkgs
conda-build:
  root-dir: /home/conda/feedstock_root/build_artifacts

==> envvars <==
bld_path: /home/conda/feedstock_root/build_artifacts

[warning] failed package validation and/or copy for commit d67b8741ffa433d88f2d4a05363ae7f9f834de5b

Hi @conda-forge/googleapis-common-protos! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's outputs did not copy from the
staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock
token. Below we have put some information about the failure to help you debug it.

Rerendering the feedstock will usually fix these problems.

If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right here.

error messages:

• invalid feedstock token

@conda-forge-admin,please add bot automerge

Solution to issue cannot be found in the documentation.

• I checked the documentation.

Issue

n/a

Installed packages

n/a

Environment info

n/a