Hello, fellow Gophers!
I have some code for which "go get -t -v" is suddenly failing for Go 1.6, complaining about a reference to the "context" package (added in 1.7).
I haven't changed any of my imports, so this means a dependency has been updated to suddenly require Go 1.7. I'm trying to figure out which package that is, and the output of "go get" doesn't seem to help much.
I develop on a Mac with OS X Sierra, so I sadly cannot really use Go 1.6 to troubleshoot in my local environment (the failing Go 1.6 build is running in Travis.) What I have tried is cleaning out my GOPATH and running the same "go get" command. Since I am running Go 1.7, it succeeds of course.
But I then used the godepgraph tool to figure out what was referencing the context package. And
nothing was, except for
golang.org/x/net/context (which does so conditionally, and would not depend on it in a Go 1.6 environment). So I'm back to square one at figuring out which package is suddenly Go 1.6-averse.
So if anyone has advice or other strategies for pinpointing my problematic dependency, I would be grateful. I am certain that "go get" has the information I seek -- it just doesn't print it out, even with the "-v" flag.
For reference, here's the output of "go get". Based on lines around the error message, I guessed it may have been
golang.org/x/text/unicode/norm, but I don't see any imports of "context" in that package:
package context: unrecognized import path "context" (import path does not begin with hostname)