#2839 Git clone from sourceforge frequently fails

[Phil Ames]

I'm trying to clone this repository from scratch, but it looks like Sourceforge's git implementation is unable to serve it. Via git:

$ git clone git://git.code.sf.net/p/net-snmp/code
Cloning into 'code'...
fatal: The remote end hung up unexpectedly

I've managed to succeed once with --depth=1 but I'd like to get more than just a shallow clone, and I can't unshallow it after checkout:
$ git fetch --unshallow
fatal: The remote end hung up unexpectedly
fatal: protocol error: bad pack header

(this happens after about 3 minutes)

Are there other git mirrors available? I couldn't find any on Github.

I'll try the https:// git checkout option but I had problems with that the last time I tried as well. Unfortunately I couldn't find a way to raise this issue with Sourceforge directly.

[Phil Ames]

The HTTPS clone failed after about 45 minutes:

$ git clone https://git.code.sf.net/p/net-snmp/code net-snmp-code
Cloning into 'net-snmp-code'...
error: RPC failed; curl 18 transfer closed with outstanding read data remaining
remote: Counting objects: 248854, done.
fatal: The remote end hung up unexpectedly
fatal: protocol error: bad pack header

[Yang Yang]

+1

I am experiencing the same problem when I am doing git pull for net_snmp, also other code repro hosted on sourceforge. Comparing with other modern git servers, such as github or gitlab, I constantly run into the issues with sourceforge, connection timeout, slow download etc. Just wondering whether we could switch over to other git servers, or at least get a backup somewhere else? Thank you!

[Keith Mendoza]

This issue has been on and off since Sourceforge did a migration. Please see Datacenter Migration Update for some info about their imgration. SF Net Ops twitter handle had information about what's causing issues in early March after their migration. It appears that these issues are back again.

[Phil Ames]

Thanks for that information, Keith. I tried raising them on Twitter here: https://twitter.com/philames/status/981350313029378048

Hopefully someone from Sourceforge can chime in or take a look.

[Robert Story]

We are looking into migrating away from SF. As a temporary workaround, I've updated my repo on github witht the latest code.

https://github.com/rstory/net-snmp.git

There is nothing we can do about their infrastructure issues.

[Trilarion]

I experience the same problem currently. Does it mean that using Git on Sourceforge is inherently unstable? It would probably make the whole thing next to useless.

[Bart Van Assche]

Since many months there are problems with git repositories hosted on SourceForge. Please use https://github.com/net-snmp instead.

[Trilarion]

It worked for me increasing the http.postBuffer as described in https://stackoverflow.com/questions/17683295/git-bash-error-rpc-failed-result-18-htp-code-200b-1kib-s

Also I must apologize, I had the same problem but with a different project's git repository, not with net-snmp. Thanks for the quick reply.