Hi Otto, On Sun, 2024-09-15 at 05:32 +0000, Nilesh Patra wrote: > Static-Built-Using is the right field. Earlier go packages were using > just Built-Using > which is a policy violation. More details at > > https://wiki.debian.org/Static-Built-Using > https://wiki.debian.org/StaticLinking#Go > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069256 [...] > Most of them are library packages which do not use such a field. You > need it for statically > linked binaries and hence only go binary packages would need such a > field. > > If that is missing in a go binary package, it is a bug and the field > should be added.
The bug linked above is pretty much to mandate the use of Static-Built- Using in the Debian Policy, so we can start filing bugs with severity: serious and update any old non-conforming packages in the Go team. New packages use Static-Built-Using (at least when dh-make-golang[1] or gophian are used). If it helps, you can read through the proposed wording[2] (and perhaps second it). -- Maytham Alsudany Debian Maintainer maytham @ OFTC maytha8 @ Libera [1]: https://github.com/Debian/dh-make-golang/blob/master/template.go#L180 [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1069256;filename=0001-Require-use-of-Static-Built-Using-to-declare-statica.patch;msg=95
signature.asc
Description: This is a digitally signed message part
