-
Notifications
You must be signed in to change notification settings - Fork 7.3k
cant clone the repo ubuntu server #2497
Comments
@Bruno-P This most likely has nothing to do with node---are you able to clone any other github repo? Try switching to http or git protocols perhaps, and just check that your own git installation works correctly in general. |
http protocol works. This problem only happens with node. I can clone any other git repo using git protocol withtout problems. |
Closing, you need to contact GitHub Support for this. |
Why close? I'm getting same issue and can't find a solution. |
@sahibalejandro --- are you able to clone with the |
Yes I did try http, https and git protocols but same result. I can clone other repos perfectly. EDIT: |
@sahibalejandro My advice is to try updating your git to the recommended version on GitHub's help pages, and if that still doesn't, work, contact GitHub support If it is indeed the case where node's repo has some misconfiguration causing this issue for you, GitHub will be able to point it out and the node people can correct it. |
Notable changes: * build: Add a --link-module option to configure that can be used to bundle additional JavaScript modules into a built binary (Bradley Meck) nodejs#2497 * docs: Merge outstanding doc updates from joyent/node (James M Snell) nodejs#2378 * http_parser: Significant performance improvement by having http.Server consume all initial data from its net.Socket and parsing directly without having to enter JavaScript. Any 'data' listeners on the net.Socket will result in the data being "unconsumed" into JavaScript, thereby undoing any performance gains. (Fedor Indutny) nodejs#2355 * libuv: Upgrade to 1.7.3 (from 1.6.1), see https://github.com/libuv/libuv/blob/v1.x/ChangeLog for details (Saúl Ibarra Corretgé) nodejs#2310 * V8: Upgrade to 4.4.63.30 (from 4.4.63.26) (Michaël Zasso) nodejs#2482
Notable changes: * build: Add a --link-module option to configure that can be used to bundle additional JavaScript modules into a built binary (Bradley Meck) nodejs#2497 * docs: Merge outstanding doc updates from joyent/node (James M Snell) nodejs#2378 * http_parser: Significant performance improvement by having http.Server consume all initial data from its net.Socket and parsing directly without having to enter JavaScript. Any 'data' listeners on the net.Socket will result in the data being "unconsumed" into JavaScript, thereby undoing any performance gains. (Fedor Indutny) nodejs#2355 * libuv: Upgrade to 1.7.3 (from 1.6.1), see https://github.com/libuv/libuv/blob/v1.x/ChangeLog for details (Saúl Ibarra Corretgé) nodejs#2310 * V8: Upgrade to 4.4.63.30 (from 4.4.63.26) (Michaël Zasso) nodejs#2482 cherry-picked from v3.x @ 1a6e52d PR-URL: nodejs/node#2653 Reviewed-By: cjihrig - Colin Ihrig <cjihrig@gmail.com>
I am trying to install node into a ubuntu server Virtual Machine and when i do git clone https://github.com/joyent/node.git i get the following error:
"fatal: https://github.com/joyent/node.git/info/refs not found. Did you run git-update-server-info on the server?"
Any suggestions?
The text was updated successfully, but these errors were encountered: