Comment 1:

Labels changed: added priority-go1, removed priority-triage.

Comment 2:

I thought this bug was about bad error messages from the Go tool if hg/git/svn weren't
found, but they're quite fine, IMO:
package code.google.com/p/rsc: exec: "hg": executable file not found in $PATH
I'm not sure we need more than that.
Then we'd be detecting which of twenty distros the user has and recommending the correct
apt-get/yum/pkg_add command.
Re-assigning back to adg.

Owner changed to @adg.

Status changed to WaitingForReply.

Comment 3:

Agree with Brad.  We used to have various hand-holding
errors in go/build and they turned out to be infinitely confusing
when they were wrong.  I deleted them all during the go/build
rewrite.
To apply to the current case, suppose we printed something
about 'you don't have Mercurial installed; run this' when in
fact they do have Mercurial installed, it's just not in their path.
Let's let the error say what it knows and not assume it knows more.
Russ

Comment 4:

In the absense of any argument, closing the bug.

Status changed to WorkingAsIntended.

Comment 5:

I would prefer it if we at least said "You need Mercurial installed" or similar. "hg"
doesn't mean anything to someone who has never used Mercurial.

Labels changed: added priority-later, removed priority-go1.

Status changed to New.

Comment 6:

Status changed to Retracted.