Martin's impression is right, and it is the go directive, not the helper. I
built the same throwaway package three times in a clean sid chroot, changing
one thing at a time:

  dh-go,     go.mod says go 1.21:  DefaultGODEBUG with 26 entries
  dh-golang, go.mod says go 1.21:  DefaultGODEBUG with 27 entries
  dh-go,     go.mod says go 1.27:  no DefaultGODEBUG at all

The two lists at go 1.21 are the same set, except dh-golang also has
panicnil=1. Same chroot, same toolchain, same `go install` command line in all
three, which the logs show.

So dh-go is not adding anything. Go bakes the GODEBUG compatibility defaults
for whatever language version the module declares, and it does that in module
mode regardless of which helper drove the build. dh-golang 1.67 builds
module-aware too when a go.mod is present, which is why it shows the same
thing.

That means the lever is upstream's go directive, and raising it is a
deliberate change of runtime behaviour for that package, not a packaging
detail: at go 1.21 the binary keeps panicnil, httpmuxgo121, tlssha1 and
x509negativeserial, and at go 1.27 it does not. Worth deciding per package
rather than across the board.

If anything is wanted from dh-go, the useful thing would be a warning when the
declared version is older than the toolchain, so the maintainer sees it at
build time instead of having to run `go version -m` on the binary. I am happy
to write that if you think it is worth having.

The package I used is 15 lines, I can put it somewhere if anyone wants to
repeat it.

Reply via email to