On Tue, 2026-08-11 at 10:07 +0200, Andrew Lee wrote: > Hi Mathias, > > On Tue, Aug 11, 2026 at 12:22 AM Mathias Gibbens <[email protected]> wrote: > > > it's probably best to just disallow an override. > > > > Yes, I concur. I'll push a commit that warns if a legacy value is > > set, and unconditionally set GO111MODULE=on. > > If we want to ensure all Go packages in Forky are built using the > modern approach. We shouldn't only just warns for legacy value, but > just simply disallow an override.
Exactly, sorry if I was unclear: https://salsa.debian.org/go-team/packages/dh-golang/-/commit/2b666a7eb0d532e69f0f23c7ec0a9917fca0d2ad. We should have a warning that appears in the build log to help assist packagers in determining why their build might start failing if they haven't properly updated their Go package. Post-forky we can drop the warning and just unconditionally set GO111MODULE=on. Mathias
signature.asc
Description: This is a digitally signed message part
