Hello, >I don't know how to handle this in the package build... Maybe I should >just disable the test suite?
maybe ask upstream for a test switch to disable a subset of tests might be good? >Is there a knob (like an environment variable) that I can use to disable >the test suite selectively when building under the buildds? I'm not aware of any of them, but I'm not that good at this programming language >In another package I maintain (monkeysign), I added an environment >variable that disables network tests in debian/rules, but that turns off >all network tests in the debian package build. Is this the same as what >I should do here? > >Are autokgtests allowed to do network requests? Maybe I should just move >the test suite there? yes, autopkgtests are allowed to do a lot of things, and this is one of the reason forthem to exist, so I think having a subset of the testsuite running during build,and one full one in autopkgtest is the best thing to do.(you might ask upstream some hints about an environment variable to selectively disable them, orsomething similar?), I really don't know if go packages have something like that... HTH, G.
