Almost all Go packages comes with some reasonable self-tests, which are
invoked by debci via 'Testsuite: autopkgtest-pkg-go'.

What do you think about suggesting this header for any golang package?

Either use 'Section: golang' or source package name of golang-* as clue
of what is a Go package.

It could be a pedantic suggestion.  Maybe even more, I don't think there
are that many false positives where this would cause any breakage.

https://lists.debian.org/debian-go/2025/09/msg00022.html

/Simon

There's already a "no-testsuite-header" tag and also "no-team-tests" tag
that exist for perl and javascript packages to point towards these testsuites.
I was thinking to use the same for go.

However, they seem to be suggesting this field based on maintainer address [1].
IOW, if lintian detects that the package belongs to the said "team" the tag gets displayed.
That makes sense because adding this seems to be written somewhere in the team policy or their
goto pages [2][3].

Now coming to golang, I have 2 questions that I am not clear about:

1. Should we suggest autopkgtest-pkg-go for only team maintained go packages?
   - I also could not find the reference to autopkgtests for golang anywhere in [4] so
     this seems not mentioned or recommended by policy as such.

2. A bunch of go packages are actual go programs, unlike perl where most packages are perl modules
   or libraries that pkg-perl maintains. And there you ought to add some tests of your own (via d/tests)
   instead of relying on the automated testsuite. Flagging these cases with "no-testsuite-header" and/or
   "no-team-tests" might cause annoyance to the maintainers. What should be done here?

[1] https://salsa.debian.org/lintian/lintian/-/blob/master/lib/Lintian/Check/Team/PkgPerl/Testsuite.pm?ref_type=heads#L44
[2] https://perl-team.pages.debian.net/autopkgtest.html
[3] https://wiki.debian.org/Javascript/Tutorial
[4] https://go-team.pages.debian.net/

Best,
Nilesh