cmd/go: try both hg and git if bitbucket API returns 403 forbidden

[gopherbot]

by shminoach:

Attempting to 'go get' a package from a private bitbucket repository fails:

package bitbucket.org/foo/bar: https://api.bitbucket.org/1.0/repositories/foo/bar: 403
FORBIDDEN

This has been reported on golang-nuts a few times:
https://groups.google.com/forum/#!topic/golang-nuts/1CBFuTZC4zU
https://groups.google.com/forum/#!topic/golang-nuts/cnhwNeR_fDE
https://groups.google.com/forum/#!topic/golang-nuts/li8J9a-Tbz0

It appears that the actual failure is during an API call that attempts to determine
whether the repo is using hg or git. I'm guessing it would be possible to work around
this by catching the 403 status code and trying hg and git each in turn.

[rsc]

Comment 1:

Labels changed: added priority-later, go1.2maybe, suggested, removed priority-triage.

Status changed to Accepted.

[rsc]

Comment 2:

Labels changed: added feature.

[robpike]

Comment 3:

Not for 1.2.

Labels changed: removed go1.2maybe.

[mitchellh]

Comment 4:

I'm sorry this isn't adding anything much to the issue, but if someone runs into this
and uses Bitbucket git repositories, this bash script is a workaround until a fix lands:
https://gist.github.com/mitchellh/6531113

[rsc]

Comment 5:

Labels changed: added go1.3maybe.

[rsc]

Comment 6:

Labels changed: removed feature.

[rsc]

Comment 7:

Labels changed: added release-none, removed go1.3maybe.

[rsc]

Comment 8:

Labels changed: added repo-main.

[gopherbot]

Comment 9:

CL https://golang.org/cl/98790043 mentions this issue.

[akaspin]

Any news? Six months!

[bradfitz]

@akaspin, nobody is working on this. And it's not scheduled for any release.

If this is affecting you, you're welcome to work on a fix.

[MyChaOS87]

any chance this gets integrated in a minor version update for at least Go1.4 as this is clearly a bug and completely preventing go get from working when using bitbucket private repositories.

[bradfitz]

Sorry, this is almost certainly below our very high bar for what goes into point releases. It's very likely the case that there will be no Go 1.4.x releases at all, with Go 1.5 right around the corner.