Linux workstation

Upstream software project

python-googleapis-common-protos

Common protobufs used in Google APIs

About python-googleapis-common-protos

Common protobufs used in Google APIs

This project links 2 native package records across 1 recorded operating-system release. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

openSUSE Tumbleweed: 2 package records. Catalog coverage diagram, not an application screenshot.python-googleapis-common-protos: recorded package coverageopenSUSE Tumbleweed2 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
python-googleapis-common-protos
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
opensuse-tumbleweed
License expression
Apache-2.0
Metadata completeness
100/100 (not a software quality rating)
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

googleapis-common-protos contains the python classes generated from the common protos in the googleapis_ repository.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

openSUSE Tumbleweed

  1. python313-googleapis-common-protos

    openSUSE Tumbleweed / Development/Languages/Python / source python-googleapis-common-protos

    1.75.1-1.1

    Common protobufs used in Google APIs

    noarchtumbleweed
  2. python314-googleapis-common-protos

    openSUSE Tumbleweed / Development/Languages/Python / source python-googleapis-common-protos

    1.75.1-1.1

    Common protobufs used in Google APIs

    noarchtumbleweed

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.