* Jochen Sprickerhof <jspri...@debian.org> [2025-07-26 08:45]:
* Mathias Gibbens <gib...@debian.org> [2025-07-19 11:40]:The root cause looks like the golang-github-golang-protobuf-1-3-dev -> golang-github-golang-protobuf-1-5-dev transition.I agree. Sadly this transition is still incomplete as there are a number of packages build depending on the old version:$ dak rm -nRb golang-github-golang-protobuf-1-3-dev protoc-gen-go-1-3 Will remove the following packages from unstable: golang-github-golang-protobuf-1-3-dev | 1.3.5-4 | all protoc-gen-go-1-3 | 1.3.5-4+b12 | riscv64 protoc-gen-go-1-3 | 1.3.5-4+b14 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, s390x Maintainer: Debian Go Packaging Team <team+pkg...@tracker.debian.org> ------------------- Reason ------------------- ---------------------------------------------- Checking reverse dependencies... # Broken Depends: golang-github-golang-protobuf-1-3: golang-goprotobuf-dev # Broken Build-Depends: golang-github-golang-groupcache: golang-github-golang-protobuf-1-3-dev golang-github-spiffe-go-spiffe: protoc-gen-go-1-3 golang-google-appengine: golang-github-golang-protobuf-1-3-dev golang-gopkg-rethinkdb-rethinkdb-go.v6: golang-github-golang-protobuf-1-3-dev protoc-gen-go-1-3 golang-protobuf-extensions: golang-github-golang-protobuf-1-3-dev golang-v2ray-core: protoc-gen-go-1-3
Actually:
coccia:~$ dak rm -nR golang-github-golang-protobuf-1-3
Will remove the following packages from unstable:
golang-github-golang-protobuf-1-3 | 1.3.5-4 | source
golang-github-golang-protobuf-1-3-dev | 1.3.5-4 | all
golang-goprotobuf-dev | 1.3.5-4+b12 | riscv64
golang-goprotobuf-dev | 1.3.5-4+b14 | amd64, arm64, armel, armhf, i386,
mips64el, ppc64el, s390x
protoc-gen-go-1-3 | 1.3.5-4+b12 | riscv64
protoc-gen-go-1-3 | 1.3.5-4+b14 | amd64, arm64, armel, armhf, i386, mips64el,
ppc64el, s390x
Maintainer: Debian Go Packaging Team <team+pkg...@tracker.debian.org>
------------------- Reason -------------------
----------------------------------------------
Checking reverse dependencies...
# Broken Depends:
golang-github-hashicorp-go-raftchunking:
golang-github-hashicorp-go-raftchunking-dev
golang-github-m3db-prometheus-client-model:
golang-github-m3db-prometheus-client-model-dev
# Broken Build-Depends:
debiman: golang-goprotobuf-dev
golang-android-soong: golang-goprotobuf-dev
golang-github-golang-groupcache: golang-github-golang-protobuf-1-3-dev
golang-github-hashicorp-go-raftchunking: golang-goprotobuf-dev (1.3.2~ >=)
golang-github-m3db-prometheus-client-model: golang-goprotobuf-dev
golang-github-spiffe-go-spiffe: protoc-gen-go-1-3
golang-google-appengine: golang-github-golang-protobuf-1-3-dev
golang-gopkg-rethinkdb-rethinkdb-go.v6: golang-github-golang-protobuf-1-3-dev
protoc-gen-go-1-3
golang-protobuf-extensions: golang-github-golang-protobuf-1-3-dev
golang-v2ray-core: protoc-gen-go-1-3
Dependency problem found.
Given those are Go packages they probably produce the same binary packages with the new protobuf version but I did not check this.
I gave this a try and golang-gopkg-rethinkdb-rethinkdb-go.v6 FTBFS with golang-github-golang-protobuf-1-5-dev:
protoc-gen-go: unable to determine Go import path for "ql2.proto"
Once this is done we can change golang-github-golang-protobuf-1-3 to contain only transitional dummy packages. This would mean the following changes:Package: golang-github-golang-protobuf-1-3-dev Description: transitional dummy package Replaces: Depends: golang-github-golang-protobuf-1-5-dev Conflicts: Breaks: Package: golang-goprotobuf-dev Depends: golang-github-golang-protobuf-1-5-dev, protoc-gen-go-1-5 Package: protoc-gen-go-1-3 Description: transitional dummy package Replaces: Depends: protoc-gen-go-1-5 Conflicts: protoc-gen-go Package: golang-github-golang-protobuf-1-5-dev Conflicts: golang-goprotobuf-dev, golang-github-golang-protobuf-1-3-dev (<< 1.3.5-4+b13) Replaces: golang-github-golang-protobuf-1-3-dev (<< 1.3.5-4+b13) Package: protoc-gen-go-1-5 Conflicts: protoc-gen-go, protoc-gen-go-1-3 (<< 1.3.5-4+b13) Replaces: protoc-gen-go-1-3 (<< 1.3.5-4+b12)Would be great if someone would pick this up but please coordinate with the release time before uploading.
The options I see are: a) Ask the release team (Cc) for tagging this bug trixie-can-defer. b) Remove the FTBFS package(s) from testing and finish the transition. c) Remove a lot of packages from testing. Cheers Jochen
signature.asc
Description: PGP signature
