Thanks for the excellent summary, Andrew!

On Wed, 2026-08-05 at 19:22 +0200, Andrew Lee wrote:
> Key Takeaways from the BoF
> ======================
> Team Policy for Module-Aware Builds:
>  Andrew will draft an updated Go Team packaging document for the
> Modern Module-Aware Build. Will post later on wiki for collaborative
> work.
> 
> Real-World Proof of Concept:
>  Mathias shared that a large, complex package `incus` already builds
> completely using dh-golang 1.66, proving that Go Workspaces builds
> well for large-scale packaging.
> 
> Unstable Timeline:
>  Mathias plan to upload the updated dh-golang to unstable in about one
> month. (Maybe before mini DebConf Winterthur, Switzerland, so people
> may hack on it during it's DebCamp. Anyone will attend mini DebConf
> Winterthur?)
> 
> Please Help Test dh-golang 1.66 in Experimental
> ======================================
> To make this transition as smooth as possible for the entire archive,
> we really need more eyes and hands on this. Please try porting your
> applications using dh-golang 1.66 from experimental now. Catching edge
> cases early will help us refine the tooling or fix corrsponding -dev
> packages in unstable before switches over as default.

  I have created a wiki page to track known issues with dh-golang that
need to be resolved before it can be uploaded to unstable[0]. At the
moment, the biggest issue is that any Go package relying on `Testsuite:
autopkgtest-pkg-go` will likely fail its autopkgtests because in that
case we don't actually generate a `go.work` file.

  I hope to address various dh-golang issues this weekend and then make
another upload to experimental. In the meantime, I'd appreciate hearing
of any other issues people have encountered attempting to build Go
packages using dh-golang from experimental.

Mathias

[0] -- 
https://wiki.debian.org/DebConf/26/Sprints/DebianGoTeam/Known-dh-golang-issues

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to