+1 -- the guide says explicit dh-go, pocketbase does that, but dh-make-golang still emits dh-sequence-golang. Meanwhile dh-golang 1.67 in unstable broke packages that had not opted in yet (#1146815). What should new go-team packages use in Build-Depends today?
El dom, 6 sept 2026 a las 8:34, Nicolas Peugnet (<[email protected]>) escribió: > > On 05/09/2026 22:57, Hermes Jesus Rodriguez Azuaje wrote: > > Hello Santiago, > > > > Bug filed against src:dh-golang: > > https://bugs.debian.org/1146815 > > > > A/B (Go 1.27.0 fixed): > > dh-golang 1.65 → PASS (golang-goji, golang-github-armon-go-metrics) > > dh-go 1.67 → FAIL (same packages; go.work / replace) > > > > So this looks like the dh-go 1.66/1.67 module-aware upload, not > > golang-1.27 alone. Helper: https://salsa.debian.org/-/snippets/871 > > @ajqlee: I don't understand, wasn't dh-go supposed to be opt-in for the > transition period, as a way to test that packages will be able to build > in the future? > > From what I see in the Transition Guide [1], the dh-go dependency have > to be explicitly specified, but when I look at the example [2] it shows > that dh-golang has to be removed. However packages initially generated > with dh-make-golang do not have an explicit dependency on dh-golang, but > only on dh-sequence-golang. > > [1]: https://wiki.debian.org/Teams/DebianGoTeam/ModuleAwareBuilds > [2]: > https://salsa.debian.org/go-team/packages/pocketbase/-/commit/4ddb91b866daf59b37def89e58cef52a92d1c65b > -- > Nicolas Peugnet
