Skip to content
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.

cant clone the repo ubuntu server #2497

Closed
brpaz opened this issue Jan 9, 2012 · 7 comments
Closed

cant clone the repo ubuntu server #2497

brpaz opened this issue Jan 9, 2012 · 7 comments

Comments

@brpaz
Copy link

brpaz commented Jan 9, 2012

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?

@adamnbowen
Copy link

@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.

@brpaz
Copy link
Author

brpaz commented Jan 21, 2012

http protocol works. This problem only happens with node. I can clone any other git repo using git protocol withtout problems.

@bnoordhuis
Copy link
Member

Closing, you need to contact GitHub Support for this.

@sahibalejandro
Copy link

Why close? I'm getting same issue and can't find a solution.

@adamnbowen
Copy link

@sahibalejandro --- are you able to clone with the http or git protocols? This issue was closed, because the user could still clone via http, and the fact that a broken protocol is a problem for GitHub Support, not for the individual git repo.

@sahibalejandro
Copy link

Yes I did try http, https and git protocols but same result. I can clone other repos perfectly.
I have git 1.7.2.5, in GitHub help says I need 1.7.10 or something like that, I think is my git version. :(

EDIT:
If is a version problem sorry for re-open the thread.

@adamnbowen
Copy link

@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.

richardlau pushed a commit to ibmruntimes/node that referenced this issue Sep 18, 2015
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
utterstep pushed a commit to lutik-inc/node that referenced this issue Sep 21, 2015
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>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants