We don't know exactly what went wrong. We can't say that the custom import changed target, because maybe it was never code.google.com/p/go.net and you just happened to run an hg command to populate /Users/r/src/golang.org/x/net from there. We could suggest removing the directory and re-running go get, but that assumes there are no changes that need to be kept. I am always wary of tools suggesting that people remove directories: people will do it blindly.

We could make the error more explicit about the operations, saying

imports golang.org/x/net/context: /Users/r/src/golang.org/x/net is checked out from https://code.google.com/p/go.net, but golang.org/x/net should be checked out from https://go.googlesource.com/net

Is that enough to make the problem clearer?

Perhaps the message should say why "golang.org/x/net should be checked out from xxx". Otherwise it's like "uhh, but why should it be checked out from there?"

golang.org/x/net is a custom import path for https://go.googlesource.com/net, but /Users/r/src/golang.org/x/net is checked out from https://code.google.com/p/go.net
?

That's much clearer IMO. LGTM.

On 14 January 2015 at 14:50, Russ Cox notifications@github.com wrote:

golang.org/x/net is a custom import path for
https://go.googlesource.com/net, but /Users/r/src/golang.org/x/net is
checked out from https://code.google.com/p/go.net
?

—
Reply to this email directly or view it on GitHub
#9540 (comment).

Fixed but forgot to write the magic line. https://golang.org/cl/2808