On Mon, Oct 26, 2020 at 11:33 AM Felix Lechner <[email protected]> wrote: > On Mon, Oct 26, 2020 at 7:48 AM Zack Weinberg <[email protected]> wrote: > > > > Go library packages bundle their own test suites, which may include > > arbitrary data files; > > Which package are you working on, please? We cannot investigate your > issue properly without a reference.
I was working on a local package for my job. I'm not a DD or even a DM nor have I had any contact with the Go team. Any golang-*-dev package where the source package contains a 'testdata' directory somewhere should show this effect -- in particular, if it contains .txt files that should trip package-contains-documentation-outside-usr-share-doc. I did nothing special to the result of running dh-make-golang on the upstream git repo. > By "Go library package" you probably mean Golang source modules. I > just checked mine; they ship testing sources but no test data. Does it > really make sense to ship either as part of the installation packages? I could be wrong, but I am under the impression that the *_test.go files and the testdata/** files are used by autopkgtest to run the test suite against the installed version of the library. If these files *aren't* used for anything, probably this bug should be reassigned to dh-golang and turned into a request to have it weed them out during the binary phase. zw
