----- Original Message ----- > From: "nicolas mailhot" <nicolas.mailhot@xxxxxxxxxxx> > To: "Jakub Cajka" <jcajka@xxxxxxxxxx> > Cc: golang@xxxxxxxxxxxxxxxxxxxxxxx, "Development discussions related to Fedora" <devel@xxxxxxxxxxxxxxxxxxxxxxx> > Sent: Monday, January 15, 2018 2:22:26 PM > Subject: Re: F28 System Wide Change: Golang 1.10a > > Hi, > > So, to be more scientific, I did a complete rebuild from scratch of my Go > spec stash in rawhide, both with Go 1.10 and forcing the previous Go 1.9.2 > (about 300 packages, some of which are not supposed to build yet because I > still need to finish the unbundling and bootstraping of docker in addition > to consul, etcd, cobra and runc) > > I have 58 more packages failing with Go 1.10 (though some are probably > fallouts that depend on a packages Go 1.10 does not like). Starting with > Google’s own golang.og/x/debug! > > Maybe Go 1.10 is not ready for use yet? Have you investigated the build failures to have such strong claim? I'm finishing going through distro wide rebuild(all ~500 packages) and roughly 74 packages are failing to build. Nearly all build failures are caused by errors(inefficiencies) in the packages code or stale/inactive packagers, with no direct relation to the go compiler itself. I see less than 1% of packages that look like candidates for golang bugs. I will post results when I finish(in ~1-2 days). JC > > Build logs of both runs by PM, they take around 100 MiB each uncompressed > > Regards, > > -- > Nicolas Mailhot > _______________________________________________ > golang mailing list -- golang@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to golang-leave@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
