[Pkg-golang-devel] Bug#780355: Build empty golang-go and golang-src packages on architectures without golang support and depend on gccgo instead

[Tianon Gravi]

On 13 March 2015 at 10:07, Matthias Klose <doko at debian.org> wrote:
> well, up to now, I only have one package with a build failure in the testsuite.

This ignores the fact that builds doesn't mean works, though.  Even
builds is questionable -- src:docker.io is a good example of a package
that needs more love to even build (which I'd reiterate _is_ happening
upstream right now), but even upstream hasn't had a chance to test
that it _works_, which is what I'm much more interested in (and which
is something that we can't just test trivially archive-wide).

In a perfect world, the project's test suite would do this work for
us, but we're definitely really far from a perfect world, especially
in the case of things like src:docker.io where upstream has a pretty
decently comprehensive test suite, but we can't run it because it
needs more extreme permissions than we can reasonably provide just for
building an arbitrary package.

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4