Hi Nicolas, On Sun, Sep 6, 2026 at 2:34 PM Nicolas Peugnet <[email protected]> wrote: > @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?
You are right. `dh-make-golang` is out of date and still generates legacy `dh-sequence-golang` setup instead of the new `dh-go` buildsystem. > 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 I noticed the same issue above when packaging `golang-github-pocketbase-ozzo-validation-v4` with a major API version /v4 in its XS-Go-Import-Path. `dh-make-golang` still generates legacy build-deps uses `dh-golang` instead of `dh-go`, and also generates legacy source, binary package names and vcs-tags without append `-v4` API verision suffix to match the upstream import path. Since `dh-make-golang` is also the primary tooling for Go packaging in Debian, having it out of date creates extra manual work and generates outdated packaging files. Does any dh-make-golang maintainers available to help to make it generates modern, module-aware configurations and handles major API version suffix correctly? Best regards, -- -Andrew
