David Coppa writes: > On Fri, Oct 17, 2014 at 8:45 PM, Stuart Henderson <st...@openbsd.org> wrote: >> On 2014/10/17 19:49, David Coppa wrote: >>> On Fri, Oct 17, 2014 at 7:46 PM, David Coppa <dco...@gmail.com> wrote: >>> > On Fri, Oct 17, 2014 at 5:34 PM, Stuart Henderson <st...@openbsd.org> >>> > wrote: >>> >> On 2014/10/15 02:54, Stuart Henderson wrote: >>> >>> Does this (log below) ring any bells? >>> >> >>> >> I didn't hit this on the next build. >>> >> >>> >>> lang/coffeescript - "npm ERR! Error: getaddrinfo EIO" >>> >> >>> >> coffeescript won't build unless it can make an https connection to >>> >> registry.npmjs.org, I didn't fancy digging into npm and it's so far >>> >> resistant to my attempts to mitm for some reason (sits with a >>> >> spinning \|/| cursor) so I'm not sure what it's trying to fetch >>> >> from there. >>> > >>> > # mitmdump --app-host npmjs.org >> >> Oh I looked at porting that but got stuck because it wanted new py-openssl >> which wanted py-cryptography which needed CFFI ... (sslsplit normally works >> but for some reason failed with this one). > > I've installed it using "pip-2.7 install mitmproxy" > >>> > 127.0.0.1 GET https://registry.npmjs.org/mkdirp >>> > << 200 OK 21.08kB >>> > 127.0.0.1 GET https://registry.npmjs.org/mkdirp/-/mkdirp-0.3.5.tgz >>> > << 200 OK 4.06kB >>> >>> So we need a new port for: >>> >>> https://github.com/substack/node-mkdirp >>> >>> to be a dependency for coffeescript... >> >> Isn't it in the main node package? > > Oh you're right, it's in the main node package. > > So why coffeescript is trying to download it from the node repo? > > I know nothing about node.js... > > Aaron?
I thought I was losing my mind.. couldn't figure out why we never noticed this before. If we can't trick npm into thinking it has the modules already installed it tries to grab them from the npmjs registry. Apparently we never noticed it because node.js shipped with version 0.3.5 of mkdirp and we were able to symlink it into the coffeescript stuff. Making a package of it now results in a collision with the nodejs package.. Sigh. --
