Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Closed
gopherbot opened this issue Apr 30, 2013 · 13 comments
Closed

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

gopherbot opened this issue Apr 30, 2013 · 13 comments
Labels
FrozenDueToAge Suggested Issues that may be good for new contributors looking for work to do.
Milestone
Go1.5

Comments

@gopherbot
Copy link

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
Copy link
Contributor

rsc commented Jul 25, 2013

Comment 1:

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

Status changed to Accepted.

@rsc
Copy link
Contributor

rsc commented Jul 30, 2013

Comment 2:

Labels changed: added feature.

@robpike
Copy link
Contributor

robpike commented Aug 30, 2013

Comment 3:

Not for 1.2.

Labels changed: removed go1.2maybe.

@mitchellh
Copy link

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
Copy link
Contributor

rsc commented Nov 27, 2013

Comment 5:

Labels changed: added go1.3maybe.

@rsc
Copy link
Contributor

rsc commented Nov 27, 2013

Comment 6:

Labels changed: removed feature.

@rsc
Copy link
Contributor

rsc commented Dec 4, 2013

Comment 7:

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

@rsc
Copy link
Contributor

rsc commented Dec 4, 2013

Comment 8:

Labels changed: added repo-main.

@gopherbot
Copy link
Author

Comment 9:

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

@gopherbot gopherbot added accepted Suggested Issues that may be good for new contributors looking for work to do. labels Apr 26, 2014
@akaspin
Copy link

akaspin commented Mar 21, 2015

Any news? Six months!

@bradfitz
Copy link
Contributor

@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.

@mikioh mikioh added this to the Go1.5 milestone Apr 9, 2015
@MyChaOS87
Copy link

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
Copy link
Contributor

bradfitz commented Jul 9, 2015

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.

@bradfitz bradfitz reopened this Jul 9, 2015
@bradfitz bradfitz closed this as completed Jul 9, 2015
@golang golang locked and limited conversation to collaborators Jul 11, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge Suggested Issues that may be good for new contributors looking for work to do.
Projects
None yet
Milestone
Go1.5
Development

No branches or pull requests
8 participants
@mitchellh @bradfitz @mikioh @rsc @akaspin @MyChaOS87 @robpike @gopherbot