Comment 4 for bug 2025668

I now start to understand what's going on. It is related to

- https://bugs.debian.org/1026139
- golang-google-grpc-dev 1.33.3-2 in Ubuntu mantic and in Debian sid
- golang-google-grpc-dev 1.38.0-5 in Ubuntu mantic-proposed

In a nutshell, from what I understand bassed on the discussions on OFTC #debian-golang IRC channel between 2023-06-23 and 2023-06-28, golang-google-grpc 1.38.0-5, still experimental in nature, got mistakenly/prematurely uploaded to Debian unstable and broke quite a few packages due to the switch from golang-github-golang-protobuf-1-3-dev to golang-github-golang-protobuf-1-5-dev.

Debian's golang-google-grpc was somehow magically reverted to 1.33.3-2 (with apt-get) and unbroke everything, even though https://tracker.debian.org/pkg/golang-google-grpc still shows 1.38.0-5.
And yes, 1.38.0-5 got sync'ed into mantic-proposed too.

Oh, wait, kibi explained that the package was actually not reverted:

<kibi> foka: we talked about doing that, but that wasn't implemented yet
<kibi> you can see the following, but that's just part of the RC bugginess:
<kibi> golang-google-grpc | 1.33.3-2 | unstable | source
<kibi> golang-google-grpc | 1.38.0-5 | unstable | source
<foka> kibi: So "apt install" sees only the first entry and installs golang-google-grpc-dev 1.33.3-2, a happy accident? I was wondering because hugo magically builds fine on buildd.debian.org while it fails on Ubuntu mantic (because mantic-proposed has golang-google-grpc 1.38.0-5)
<kibi> I think an accident, due to the way architecture: all packages are exposed. Since there are missing builds for the new version, I think the old binaries are still exposed in binary-<arch> Packages.

I guess we'll wait until "1.XX.is-really.1.33.3-2 revert" is uploaded before hugo build would pass.
Let's continue with this sync request after that? :-)

Thanks again!