Comment 5 for bug 1392094

I'm actually really concerned by this change (speaking as both a Debian maintainer on the package, and as the maintainer of the build scripts upstream). We're actively working upstream on getting proper first-class gccgo compilation support into Docker's build system (https://github.com/docker/docker/issues/9207 for the tracker upstream), but one of the things we've noticed is that just because it doesn't FTBFS doesn't mean it actually works. Have you run it against the upstream integration tests to at least get an initial verification that the daemon works as expected?