> The "go" implementation bundled there is not fully-baked. For > example, using "go get" to download a project didn't bother > downloading the dependencies like it should, thus causing the build to > fail really hard with a screen-full of errors.
GCC 5 is not yet released. That's why it is in experimental. The specific issue here is https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65462 which is meanwhile fixed in experimental. Yes, unfortunately I had to find out myself about that one ... > > ... claims to be compatible with Go 1.4. > > In my own testing, this claim is dubious at best. The language > support itself may be compatible (I didn't test it thoroughly enough > to say for sure), but the tooling certainly isn't yet. Does your testing goes beyond docker.io? If no, I would claim your testing is dubious at best ;) There are certainly still issues, but to me it starts to look usable. There are other dubious things like how golang-gotools is built in Debian ... I appreciate the testing you do, and I'm interested to see gccgo specific bug reports, if these are reproducible with Go 1.4.2. And yes, I would appreciate a golang-gotools built from the 1.4 branch in experimental too (golang is outdated in experimental, so I updated myself to 1.4.2 and uploaded a package to the Launchpad PPA ~doko/toolchain). Matthias -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
