Hi

The golang-google-cloud package upstream is a multirepo, and we track
the vX.Y.Z tags, with the latest one being v0.123.0 from September 2025.

It seems upstream has stopped making these generic v* release tags.

What I've noticed is that updating several crypto-related packages now
has build failure due to some ML-DSA identifiers being added to
golang-google-cloud's kms/ sub-directory.  They are part of the kms/v*
tags, e.g. kms/v1.37.0, but that is not in upstream git master.

Any thoughts on how to approach updating this package?

My first inclination was to track upstream git master instead, but some
components doesn't seem to get merged back into master.

Another solution is to do a separate package for interesting
sub-directories with faster release cadence.  But we already discussed
this, and I agree the general preference is to not do that.

I'm considering adding the newer kms/ files as vendored files, with some
explanation in README-source, but it is not a great long-term solution.

Going fancy we could make this a multi-orig-tarball debian package, but
creating a proper debian/watch setup for this package seems beyond my
ability -- it has hundreds of sub-modules, and I wonder if the
multi-orig-tarballs approach really handle this well.

What's the least worst solution?  I doubt we will be able to implement
an ideal solution here in the near term.

/Simon

Attachment: signature.asc
Description: PGP signature

Reply via email to