Sync hugo 0.113.0-2 (universe) from Debian unstable (main)

Looks good; I'll set this going. Thanks!

Oh dear, that doesn't seem to like building: https://launchpad.net/ubuntu/+source/hugo/0.112.7-1 -- I note Debian sid is now on 0.113.0-1. Is it worth sync'ing that instead?

Hi Dave,

Thank you so much for looking into this, and for letting me know of the FTBFS:

    # google.golang.org/grpc/binarylog/grpc_binarylog_v1
    src/google.golang.org/grpc/binarylog/grpc_binarylog_v1/binarylog.pb.go:46:17: undefined: proto.ProtoPackageIsVersion4

Yes, 0.113.0-1 is worth sync'ing instead of 0.112.7-1, though I suspect it would stop at the same "undefined: proto.ProtoPackageIsVersion4" error.

May I get back to you in a day or two? I will try building this package on mantic and try to find a solution.

Thanks and Cheers!

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!

> 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? :-)

Sure, no hurry! I'll try and keep an eye on this (I'm now subscribed to the bug), but if I'm too slow getting back to you, do feel free to throw ubuntu-sponsors back in the subscribe list. The sponsorship queue's getting a lot more attention recently and it should be serviced pretty quickly.

Thank you Dave!

Good news! golang-google-grpc-dev 1.38.0+really1.33.3-1 has landed in mantic-proposed!

And hugo 0.113.0-1 built successfully inside my local LXD VM^H^H container running mantic too,
so yes, when you are free, please try sync'ing hugo from Debian again,
and see if it builds to the end (keeping my fingers crossed...)

Many thanks!

Heh - I was about to go sync this, this morning and Launchpad beat me to it! I guess once syncpackage removes the delta, even if it's subsequently unsuccessful in building, the auto-sync takes over and hence 0.113.0-1 is already in the -proposed pocket.

Unfortunately it's also failed to build on all archs, though the error looks quite different. I haven't been through the logs on all the archs yet, but the amd64 one at least looks to be a trivial case of the test-suite trying to reach the internet:

ERROR 2023/07/05 20:46:57 Failed to get JSON resource "https://publish.twitter.com/oembed?dnt=false&url=https%3A%2F%2Ftwitter.com%2F1626985695280603138%2Fstatus%2F877500564405444608": Get "https://publish.twitter.com/oembed?dnt=false&url=https%3A%2F%2Ftwitter.com%2F1626985695280603138%2Fstatus%2F877500564405444608": dial tcp: lookup publish.twitter.com on 127.0.0.53:53: no such host

This bug was fixed in the package hugo - 0.113.0-2

---------------
hugo (0.113.0-2) unstable; urgency=medium

  * Skip TestEmbeddedShortcodes except during autopkgtest
    as the tested {{< tweet >}} shortcode needs access to the internet.
    Thanks to Dave Jones for helping me with syncing to Ubuntu! (LP: #2025668)

 -- Anthony Fok <email address hidden> Thu, 06 Jul 2023 09:15:58 -0600