-
Notifications
You must be signed in to change notification settings - Fork 29
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.
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
Some gopkg.in repos produce "no HEAD branch" error. #72
Comments
Thanks for reporting this. I'll be able to look more into it after Friday. Off the top of my head (no pun intended), I've seen similar things in the past, and I think this might be related to gopkg.in service doing a hacky edit on the git information it serves, which does not quite match what a normal repository would serve. The solution might be to try to submit a PR to gopkg.in to make it serve git information that's more in line with what one would expect, or update Go Package Store to be able to deal with it. Two questions:
|
Ok, I can reproduce too:
It also affects
|
Yes.
For completeness, this is |
I also thought |
The underlying issue is in
Basically, it's not able to deduct what is the "default branch" from the remote. Given that I'll look more into it after Friday. |
No hurry, just wanted to bring it up so I wouldn't forget about it :) Thanks for looking into it! |
I've created niemeyer/gopkg#54 which I believe is the root issue that needs to be resolved. Once it is, everything here should work. I could try to add some hacky workarounds for Below are some notes for my reference.
|
Now it also throws
|
That's unexpected. Was it a one-off thing, or does it happen reproducibly? What does |
Apologies for the late reply.
Ran again today, the same output.
Note that the branch is Edit: by above I meant #73. |
Also, running the latest version of your programs and their deps (unless |
Thanks. I investigated the |
Also seeing the same or similar issue:
|
@bits01, this issue is about gopkg.in repos only (I've renamed it to better reflect that). What you're seeing is not gopkg.in, so it might be a real issue. Can you open a new issue and provide more information on how I can reproduce it? |
I got the following:
I went to the repo, confirmed it was on
master
trackingorigin/master
, did agit pull
and it worked, pulling a few new commits that hadn't been fetched yet.Also confirmed that
HEAD
exists and points to the same commit asmaster
.What could have caused that error?
Even after doing those commands and being up to date, I still get the same error. I can give you a full copy of the repo clone in this state that triggers the bug.
The text was updated successfully, but these errors were encountered: