Hi all,
I mentioned this on the IRC channel, but am also bringing it up here.
A couple of days ago a handful of bookworm -> trixie upgrade bugs were
reported, all relating to packages that depend on protobuf: #1109513,
#1109514, #1109515, #1109516, #1109517.
The root cause in each bug seems to be the golang-github-golang-
protobuf 1-3 -> 1-5 transition. Here's what apt reports:
> root@saved-quagga:~# apt dist-upgrade -o Debug::pkgProblemResolver=true
> Starting pkgProblemResolver with broken count: 2
> Starting 2 pkgProblemResolver with broken count: 2
> Investigating (0) golang-github-golang-protobuf-1-3-dev:amd64 < 1.3.5-4 @ii mK Ib >
> Broken golang-github-golang-protobuf-1-3-dev:amd64 Conflicts on golang-github-golang-protobuf-1-5-dev:amd64 < none -> 1.5.4-1 @un uN Ib >
> Considering golang-github-golang-protobuf-1-5-dev:amd64 -1 as a solution to golang-github-golang-protobuf-1-3-dev:amd64 0
> Added golang-github-golang-protobuf-1-5-dev:amd64 to the remove list
> Fixing golang-github-golang-protobuf-1-3-dev:amd64 via keep of golang-github-golang-protobuf-1-5-dev:amd64
> Investigating (0) golang-gomega-dev:amd64 < 1.10.3-1 -> 1.36.2-1 @ii umU Ib >
> Broken golang-gomega-dev:amd64 Depends on golang-github-golang-protobuf-1-5-dev:amd64 < none | 1.5.4-1 @un uH >
> Considering golang-github-golang-protobuf-1-5-dev:amd64 -1 as a solution to golang-gomega-dev:amd64 0
> Holding Back golang-gomega-dev:amd64 rather than change golang-github-golang-protobuf-1-5-dev:amd64
> Try to Re-Instate (1) golang-gomega-dev:amd64
> Done
> Entering ResolveByKeep
> Not upgrading:
> golang-gomega-dev
>
> Summary:
> Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 1
I'm not sure what the correct fix is here; I'm also still making my
way home from DebConf, so if someone else can fix this please do so.
The window for getting this fixed up before the full trixie freeze
starts is pretty small.