Comment 1:

Labels changed: added go1.1.

Comment 2:

I'd like to take a stab at this as I have a strong incentive to make this better for
people on the IRC channel.
Here are some suggestions i've played around with
% go build foo/quxx
can't load package: package foo/quxx: import "foo/quxx": cannot find package in
$GOROOT="/home/dfc/go" or $GOPATH="/home/dfc"
This is the original suggestion, but I think it lacks something as GOPATH for example
doesn't actually mention /home/dfc/src, where src is the crucial bit that trips up a lot
of people.
% go build foo/quxx
can't load package: package foo/quxx: import "foo/quxx": cannot find package in
["/home/dfc/go/src/pkg" "/home/dfc/src"]
This is a different version using ctxt.SrcDirs(), which gives the canonical list of
paths that would be searched for the package, but doesn't explain how they are
discovered, and in the case that GOPATH was not set, would only list the GOROOT derived,
/home/dfc/go/src/pkg. This has the downside of leading users into trying to set GOPATH
somewhere inside GOROOT, or using sudo.

Owner changed to @davecheney.

Comment 3:

It's fine to make the error multiple lines:
cannot find "foo/quux" in any of:
    /home/rsc/g/go/src/pkg/foo/quux (from $GOROOT)
    /home/rsc/goroot1/src/foo/quux (from $GOPATH)
    /home/rsc/goroot2/src/foo/quux
cannot find "foo/quux" in any of:
    /home/rsc/g/go/src/pkg/foo/quux (from $GOROOT)
    ($GOPATH not set)

Comment 4:

Can do.

Comment 5:

Labels changed: added size-m.

Comment 6:

Labels changed: added suggested.

Comment 7:

https://golang.org/cl/6899057

Status changed to Started.

Comment 8:

This issue was closed by revision 11d96dd.

Status changed to Fixed.