#1004534 Please promote version 1.38.0-1 to unstable

#1004534#5
Date:
2022-01-30 02:49:04 UTC
From:
To:
Please upload 1.38.0-1 to unstable so that it can be used for packages there. It's a requirement to upload dnscrypt-proxy 2.1.1 for example.
#1004534#12
Date:
2023-01-22 20:10:05 UTC
From:
To:
Dear maintainers of the Debian Go Packaging Team,

I would like to second Eric's wish to upload the version in experimental
(or perhaps a newer one) to unstable too, so that it can make its way to
bookworm before the freeze.  Or is there any reason (that of course I
don't know) why it has to be a version like 1.33.3 instead?

AFAICS golang-google-grpc is the only dependency left that prevents the
upgrade of golang-github-powerman-check whose previous version (that is
still in sid) is known to FTBFS and so in turn prevents even the
migration of dnscrypt-proxy's older version 2.0.45 that currently is in
bullseye but is not going to be in bookworm unless anything is going to
happen.
Would you agree to switch the severity of this ticket from "wishlist" to
"normal" or even "important" to reflect this situation?

Best regards,

Thomas Uhle

#1004534#17
Date:
2023-01-23 13:14:02 UTC
From:
To:
It's too late. By bumping to 1.33.3 already takes a lot of time for me.

Please be aware that a library like grpc-go is very essential in the
Go ecosystem. Updating the version not only means just packaging the
new version. You need to take care of the reverse dependencies.

I'm not holding others to update the version. But no one shows the
plan to ensure a smooth transition.

#1004534#26
Date:
2024-06-29 11:17:16 UTC
From:
To:
I just realized that we have an open bug that we can use to track this,
so let me post a status with some context.
Status update:

*golang-google-cloud:* I've uploaded a new version of the package to
experimental that disables
a few packages and thus closes #1074133. I think this should unblock this
transition. I'd like to note
that the package is badly outdated, but updating it is quite tricky, see
#991942 for details.

*golang-github-grpc-ecosystem-grpc-gateway*, -- updating this package away
from the protobuf APIv1
is not going to work. It seems that moving the codebase to APIv2 (which is
implemented by
golang-github-golang-protobuf-1-5-dev and golang-google-protobuf-dev), is
what upstream implemented in
their [grpc-gateway@v2.0.0] release. Thankfully, we have that already
packaged in debian as
golang-github-grpc-ecosystem-grpc-gateway.v2-dev, currently in experimental
only, because it depends
on the newer grpc.

So in order to make progress, I propose that we retire
the golang-github-grpc-ecosystem-grpc-gateway-dev
package in favor of golang-github-grpc-ecosystem-grpc-gateway.v2-dev. For
this, the following packages
need to be updated:

siretart@x1:~ $ build-rdeps --distribution testing --old
golang-github-grpc-ecosystem-grpc-gateway-dev
Reverse Build-depends in testing/main:
--------------------------------------

golang-github-kurin-blazer
golang-github-census-instrumentation-opencensus-proto
prometheus
etcd
golang-github-backblaze-blazer

Found a total of 5 reverse build-depend(s) for
golang-github-grpc-ecosystem-grpc-gateway-dev.

I'll file bugs against those five packages and will try to get them updated
to build against
grpc-gateway.v2 that we have in experimental.

 [grpc-gateway@v2.0.0]
https://github.com/grpc-ecosystem/grpc-gateway/releases/tag/v2.0.0