Go in vivid

[Matthias Klose]

As part of packaging GCC 5, there is now also a gccgo-5 package in vivid.  GCC 5
now builds the go and gofmt commands from it's own source, so the gccgo-go
package was removed from the distro.  gccgo is now based on Go 1.4.2, while
golang still stays at 1.3.  There is a hack in the golang package in that it
builds empty golang-go and golang-source packages, just to see what can be built
in the archive, and a lot of things build (including lxd and docker.io), even on
powerpc after tweaking things.

A backport for trusty can be found in the ubuntu-toolchain-r/test PPA.

A co-worker mentioned they would consider filing a FFe for golang, so it may be
useful to look at the things that will break and need an update, including some
packages for the phone, so here are some findings (didn't investigate for all of
these if these are gccgo specific things, or just exposed by Go 1.4).

  Matthias

aptly
    needs at least golang-go.tools built.

golang-go.tools
    https://launchpad.net/bugs/1409005
    Package needs an update to the 1.4 branch.

ciborium
    https://launchpad.net/bugs/1431872
    the code is not ready for Go 1.4.
    Embeds qml.v0.

libguestfs
    https://launchpad.net/bugs/1431994
    still not sure if a go 1.4 issue, or gccgo.

hockeypuck
    https://launchpad.net/bugs/1436135
    only enabled for amd64 i386
    not sure if a go 1.4 issue, or gccgo.

pollen
    only enabled for amd64 i386

ubuntu-push, account-polld:
    https://launchpad.net/bugs/1431486

    It looks like many of the libraries are not passed
    to the final link call (seen by calling go with -x).
    Is there anything which should "push" these arguments
    to the final link call?

golang-goyaml
    https://launchpad.net/bugs/1431850
    test failures when built with gccgo.

golang-log4go
    https://launchpad.net/bugs/1431851
    test failures when built with gccgo.