I'm sorry to hear that you're having issues. The Go tool should detect that a cached package in $GOPATH/pkg is out of date and overwrite it. If this is not happening reliably this may be a bug.
Can you give some details about what you tried, what you expected to happen and what happened instead. In particular, do your team use go build or go install ? On Thursday, 15 September 2016 04:31:24 UTC+10, Tom Elliott wrote: > > We've recently migrated from Go 1.6 to 1.7 within our engineering team, > and have been experiencing some binary compatibility issues (as is to be > expected) that have usually been corrected by emptying $GOPATH/pkg and > rebuilding - this was recommended but as is the case with manual steps, > people often skipped it. > > Are there any other pitfalls that people have encountered migrating > between point releases of Go? Better still, does anyone know of any tools > we could include in our builds to sanity check the contents of $GOPATH/pkg? > > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
