-
Notifications
You must be signed in to change notification settings - Fork 82
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
lineman install can't connect to git for cscodegen #351
Comments
Sounds like a connectivity issue. Not able to replicate over here and that repo is still live. On Wed, Feb 25, 2015 at 9:55 PM, aspergillusOryzae
|
I am behind a proxy, but was able to do the following commands (as well as set this up on another computer a few months ago in the same conditions):
|
I also did |
Interestingly using the versions of npm and nodejs from apt-get provide the most success, and it also seems to only be that one repos - though yes I could see its still up, but I had trouble cloning it behind the proxy or with the http url:
|
-- update -- |
This is a pretty common symptom of being behind a firewall; we've seen this at some clients with network restrictions in place. Given you've already done My experience with any other method, including proxies, local caches or mirrors of the npm repo has been fraught with nothing but headaches :( |
I am having trouble installing lineman - first I tried with the apt-get version of node and npm, then with node 0.10.32, 0.12.X, and now 0.10.36 (because cscodegen requests node 0.8.x through 0.10.x).
npm WARN engine coffee-script-redux@2.0.0-beta8: wanted: {"node":"0.8.x || 0.10.x"} (current: {"node":"0.12.0","npm":"2.5.1"})
I am running into the same issue across all node/npm version when the script is attempting to grab cscodegen from git.
The text was updated successfully, but these errors were encountered: