-
Notifications
You must be signed in to change notification settings - Fork 399
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
go get currently fails to download dnscontrol #757
Comments
CC: @jpbede I'm seeing the same thing for fresh clones. My existing repo is fine. |
I will have a look at this later on. |
It seams to me that you have already fixed that @tlimoncelli ? |
Umm... I'm not sure if I fixed it. While investigating I spotted a problem with .gitignore and I fixed that. ("zones" was ignored, not "/zones", which lead to part of Does that fix the problem for everyone? I still get the error if I unset GOPATH but that might be something funny in my environment. |
Hmm i can't reproduce it anymore after your |
@robotmay Can you confirm? |
@tlimoncelli Still getting it on my local machine. Is there anything I'd need to do to clear a cache of some sort? |
Hmm.... the ~/pkg directory is a cache. You can remove it, but I don't think that's related to this problem. What's your GOPATH variable set to? |
`~/.go` on this machine. I'll try rerunning my CI tasks too and see what happens there.
…-------- Original Message --------
On 2 Jun 2020, 15:37, Tom Limoncelli wrote:
Hmm.... the ~/pkg directory is a cache. You can remove it, but I don't think that's related to this problem.
What's your GOPATH variable set to?
—
You are receiving this because you were mentioned.
Reply to this email directly, [view it on GitHub](#757 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AAAXARNHPI4Q4DD3R3KHEOLRUUFBLANCNFSM4NQRFIZQ).
|
@tlimoncelli, @jpbede Looks to be solved on my CI 👍 Thanks for the quick fix! 😄 |
Haven't seen any other reference to this so far, but this is currently happening to me on both my CI and my local machine:
This seems to imply a breaking change upstream but I haven't had a chance to look into it properly yet.
The text was updated successfully, but these errors were encountered: