Hi, BTW I have a set of Go packages I was preparing for inclusion that build fine with Go 1.8 in Epel 7 but not with Go 1.9 in rawhide. Is there a way to check if it's a problem with the future Go 1.9 toolchain or a problem in the upstream code? I haven't have the time to investigate yet. Regards, -- Nicolas Mailhot _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
