8000 apm not respecting git config --global url."https://".insteadOf git:// · Issue #106 · atom/apm · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

apm not respecting git config --global url."https://".insteadOf git:// #106

Closed
ceeeKay opened this issue May 9, 2014 · 6 comments
Closed

apm not respecting git config --global url."https://".insteadOf git:// #106

ceeeKay opened this issue May 9, 2014 · 6 comments
Labels
bug

Comments

@ceeeKay
Copy link
ceeeKay commented May 9, 2014

Attempting to build Atom on a system behind a firewall that doesn't allow the git:// protocol out.

My ~/.gitconfig contains

[url "https://"]
    insteadOf = git://

As far as I can tell this seems to be an apm issue, but I'm not sure if it could be in atom or npm code (the lines are unclear to me).

  SOLINK_MODULE(target) Release/obj.target/git.node
  SOLINK_MODULE(target) Release/obj.target/git.node: Finished
  COPY Release/git.node
make: Leaving directory `/build/ceeeKay/atom/node_modules/git-utils/build'

npm WARN engine specificity@0.1.3: wanted: {"node":"~0.8.x"} (current: {"node":"v0.10.26","npm":"1.4.4"})
npm WARN engine specificity@0.1.3: wanted: {"node":"~0.8.x"} (current: {"node":"v0.10.26","npm":"1.4.4"})
npm ERR! git clone git://github.com/atom/slick.git Cloning into bare repository '/users/ceeeKay/.atom/.node-gyp/.atom/.apm/_git-remotes/git-github-com-atom-slick-git-fe3034e1'...
npm ERR! git clone git://github.com/atom/slick.git 
npm ERR! git clone git://github.com/atom/slick.git fatal: unable to connect to github.com:
npm ERR! git clone git://github.com/atom/slick.git github.com[0: 192.30.252.129]: errno=Connection timed out
npm ERR! Error: Command failed: fatal: unable to connect to github.com:
npm ERR! github.com[0: 192.30.252.129]: errno=Connection timed out
npm ERR! 
npm ERR! 
npm ERR!     at ChildProcess.exithandler (child_process.js:637:15)
npm ERR!     at ChildProcess.EventEmitter.emit (events.js:98:17)
npm ERR!     at maybeClose (child_process.js:743:16)
npm ERR!     at Socket.<anonymous> (child_process.js:956:11)
npm ERR!     at Socket.EventEmitter.emit (events.js:95:17)
npm ERR!     at Pipe.close (net.js:465:12)
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/npm/npm/issues>

npm ERR! System Linux 2.6.32-431.11.2.el6.centos.plus.x86_64
npm ERR! command "/build/ceeeKay/atom/apm/node_modules/atom-package-manager/bin/node" "/build/ceeeKay/atom/apm/node_modules/atom-package-manager/node_modules/npm/bin/npm-cli.js" "--userconfig" "/build/ceeeKay/atom/apm/node_modules/atom-package-manager/.apmrc" "install" "--target=0.11.10" "--arch=x64" "--quiet"
npm ERR! cwd /build/ceeeKay/atom
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.4
npm ERR! code 128
npm ERR! git clone git://github.com/benogle/jsdiff.git Cloning into bare repository '/users/ceeeKay/.atom/.node-gyp/.atom/.apm/_git-remotes/git-github-com-benogle-jsdiff-git-b9e372e4'...
npm ERR! git clone git://github.com/benogle/jsdiff.git 
npm ERR! git clone git://github.com/benogle/jsdiff.git fatal: unable to connect to github.com:
npm ERR! git clone git://github.com/benogle/jsdiff.git github.com[0: 192.30.252.129]: errno=Connection timed out
npm ERR! git clone git://github.com/kevinsawicki/jasmine-node.git Cloning into bare repository '/users/ceeeKay/.atom/.node-gyp/.atom/.apm/_git-remotes/git-github-com-kevinsawicki-jasmine-node-git-7c50cc1a'...
npm ERR! git clone git://github.com/kevinsawicki/jasmine-node.git 
npm ERR! git clone git://github.com/kevinsawicki/jasmine-node.git fatal: unable to connect to github.com:
npm ERR! git clone git://github.com/kevinsawicki/jasmine-node.git github.com[0: 192.30.252.129]: errno=Connection timed out
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /build/ceeeKay/atom/npm-debug.log
npm ERR! not ok code 0
@ceeeKay ceeeKay mentioned this issue May 9, 2014
Closed
7 tasks
@ceeeKay
Copy link
Author
ceeeKay commented May 12, 2014

This appears to be an npm issue... see npm/npm#5257 for work-around/hack (I don't know javascript/node well enough to propose a real patch)

@thedaniel thedaniel mentioned this issue May 13, 2014
Closed
@neocotic
Copy link

I'm also seeing this. I've worked around npm and git remote URL proxy issues all the way down to this one but I'm now stuck here. Would love to hear if anyone has a solution.

@ceeeKay
Copy link
Author
ceeeKay commented May 19, 2014

@neocotic My post in npm/npm#5257 contains a verified work-around.
You'll want to find . -name cache.js and edit the file found. Search for the function addRemoteGit and you'll see some other lines replacing ssh, etc. add the line u = u.replace(/^git/, "https") and it will work around it for cases where your firewall is blocking git:// protocol/port.

@neocotic
Copy link

I saw that workaround since but have stopped trying right now as it's getting to a point where I'm hacking code to support something that should be working. I've also heard that I'll just hit another wall with the shell not building on anything other than Ubuntu so I've given up.

@Azerothian
Copy link

i use this version

u = u.replace(/^git:/, "https:")

as this

u = u.replace(/^git/, "https")

can cause "npm ERR! git clone https+https://github.com/kevinsawicki/minimatch.git Cloning"

for reference, you need to edit this file when trying to build atom

\atom\apm\node_modules\atom-package-manager\node_modules\npm\lib\cache.js

@deepak1556 deepak1556 mentioned this issue May 29, 2014
Closed
@hanjos hanjos mentioned this issue Dec 23, 2014
Closed
@papodaca papodaca mentioned this issue Mar 9, 2015
Closed
@lexi-lambda lexi-lambda mentioned this issue Feb 12, 2016
Closed
@winstliu
Copy link
Contributor
winstliu commented Jun 2, 2016

Closed upstream, so I'm going to close this as well.

@winstliu winstliu closed this as completed Jun 2, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@probablycorey @Azerothian @neocotic @ceeeKay @winstliu
0