Closed foolip closed 7 years ago
This is a fundamental issue with Go itself; offering library imports by network location necessarily is subject to temporary network issues.
gopkg.in
is generally quite reliable, and it's working for me as of this writing. HTTP 301 is a redirect, which is not happening now, so probably there was a momentary misconfiguration on the server side.
In particular, this is not an skicka issue.
It is still happening for me, including if I try git clone https://gopkg.in/gcfg.v1
directly. Is nobody else having this problem?
Are you behind a firewall/proxy maybe? Try this and see if you get 200 or 301:
curl -A git/2.0.0 -I https://gopkg.in/gcfg.v1.git
$ curl -A git/2.0.0 -I https://gopkg.in/gcfg.v1.git
HTTP/1.1 200 OK
Content-Type: text/html
Date: Tue, 14 Feb 2017 03:17:07 GMT
I believe that this is an issue with the latest version of git, as described here: https://github.com/niemeyer/gopkg/issues/50.
I've found that the suggested fix, running:
% git config --global http.https://gopkg.in.followRedirects true
fixes it for me.
On Mon, Feb 13, 2017 at 7:17 PM, Philip Jägenstedt <notifications@github.com
wrote:
$ curl -A git/2.0.0 -I https://gopkg.in/gcfg.v1.git HTTP/1.1 https://gopkg.in/gcfg.v1.gitHTTP/1.1 200 OK Content-Type: text/html Date: Tue, 14 Feb 2017 03:17:07 GMT
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/google/skicka/issues/109#issuecomment-279596277, or mute the thread https://github.com/notifications/unsubscribe-auth/AAGQpwlCyxWfrF8d-_-TqTvOUNfvIQ8nks5rcRzTgaJpZM4Lbyj9 .
Looks like that was a very deliberate change in https://github.com/git/git/commit/50d3413740d1da599cdc0106e6e916741394cc98 but I guess https://github.com/niemeyer/gopkg/issues/50 is enough to track that, so feel free to close this.
No need to change the configuration anymore. We've changed gopkg.in itself to support the new git quirks.
Perhaps the gcfg.v1 repo should be copied, if the hosting of it is not reliable?