Hi Niliesh and Team, Thank you for spoting this issue. It was intended to block additional work in unstable due to we are in module-aware builds transition.
Sorry everyone. I supose should prepare a report for Go Team Sprint right after DebConf to explain what happened, where we are and what are still missing for the Module-Aware Builds transition. After the heavy workload during the sprint, I was completely exhasted and got sick after I arrived home. During mini DebConf Hamburg, I have addressed the critical runtime and security issue caused by our legacy GOPATH build mode (which forces GO111MODULE=off and injects legacy DefaultGODEBUG flags into Go binaries). So that Toddy already made dh-golang 1.64 to ship all go.mod files, and dh-golang 1.66( currently in experiemntal) which enables modue-aware builds. I also addressed it once more in my talk during DebConf: https://debconf26.debconf.org/talks/87-rescue-forky-we-have-go-time-travel-to-2011-building-go-like-its-2011-is-broken/ Keep working on old GOPATH mode into unstable keeps Go Ecosystem is broken in Debian. To make the transition possible. We need real world testing to catch and fix all the edge cases early. I strongly encourage everyone to start porting your Go applications using dh-golang 1.66 from experimental and report any issues you run into. We need help hands from everyone to polishing the tooling. I will try to complete the report for Go Team Sprint ASAP once I fully recovered. Best regards, -Andrew On Sun, Aug 2, 2026 at 5:56 AM Nilesh Patra <[email protected]> wrote: > > Hi Marcos, > > You did an upload for aerc recently but seemed to have pushed changes meant > for experimental > in debian/sid branch itself. I was working on it and noticed that the ci > would keep failing > and I will need to revert your changes if I want to upload this to unstable. > > Please push to debian/experimental branch in future. You can create this > branch if it does not > already exist. > > Thanks! > Nilesh > -- -Andrew
