Hi Ansgar, On Sun, Aug 2, 2026 at 3:53 PM Ansgar <[email protected]> wrote: > The python3-protobuf packages in Debian experimental switched to a > different version scheme: It follows upstream versioning [1]. Under v36.0-rc1 it lists Python.
> But 36.0~rc1 is not the version number that is used by upstream for > releases on Pypi. The current version there is 7.36.0rc1. > > Debian omits the major version part. As noted, Debian packaging comes from the upstream repository [2] where it has 36.0 RC1 as version number. > I think that is confusing and python3-protobuf versions should match > the versions that upstream uses for Pypi releases. Everything else > seems to be very fragile for versioned dependencies on > python3-protobuf. Does the package version matter on Python version detection? I think dependant packages may check the version number directly: $ python3 >>> from google.protobuf import runtime_version >>> print(runtime_version.OSS_MAJOR, runtime_version.OSS_MINOR, >>> runtime_version.OSS_PATCH) 7 36 0 > (This might require that src:protobuf overrides the "Version" field > for some binary packages.) Can you show me examples of such packages? I've never done a package binary version override. Cheers, Laszlo/GCS [1] https://github.com/protocolbuffers/protobuf/releases [2] https://github.com/protocolbuffers/protobuf/tree/v36.0-rc1/python
