search

Sean-Der / fail2web

a fail2ban GUI powered by fail2rest
536 stars 48 forks source link

npm build fails #25

Closed Deepcuts closed 9 years ago

Deepcuts commented 9 years ago

Hello,

After having some problems with go version, now I am stuck at "npm build":

root@ns4:/home/edited/public_html/f2r/fail2web/.git# npm install npm http GET https://registry.npmjs.org/watchify npm http GET https://registry.npmjs.org/lodash npm http GET https://registry.npmjs.org/brfs/1.0.2 npm http GET https://registry.npmjs.org/angular npm http GET https://registry.npmjs.org/browserify-shim npm http GET https://registry.npmjs.org/insert-css npm http GET https://registry.npmjs.org/bootstrap npm http GET https://registry.npmjs.org/browserify npm http GET https://registry.npmjs.org/d3

npm ERR! Error: failed to fetch from registry: lodash npm ERR! at /usr/share/npm/lib/utils/npm-registry-client/get.js:139:12 npm ERR! at cb (/usr/share/npm/lib/utils/npm-registry-client/request.js:31:9) npm ERR! at Request._callback (/usr/share/npm/lib/utils/npm-registry-client/request.js:136:18) npm ERR! at Request.callback (/usr/lib/nodejs/request/main.js:119:22) npm ERR! at Request. (/usr/lib/nodejs/request/main.js:212:58) npm ERR! at Request.emit (events.js:88:20) npm ERR! at ClientRequest. (/usr/lib/nodejs/request/main.js:412:12) npm ERR! at ClientRequest.emit (events.js:67:17) npm ERR! at HTTPParser.onIncoming (http.js:1261:11) npm ERR! at HTTPParser.onHeadersComplete (http.js:102:31) npm ERR! You may report this log at: npm ERR! http://bugs.debian.org/npm npm ERR! or use npm ERR! reportbug --attach /home/edited/public_html/f2r/fail2web/.git/npm-debug.log npm npm ERR! npm ERR! System Linux 3.13.0-36-generic npm ERR! command "node" "/usr/bin/npm" "install" npm ERR! cwd /home/edited/public_html/f2r/fail2web/.git npm ERR! node -v v0.6.12 npm ERR! npm -v 1.1.4 npm ERR! message failed to fetch from registry: lodash npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /home/edited/public_html/f2r/fail2web/.git/npm-debug.log npm not ok

Any clue how to get past this please?

Sean-Der commented 9 years ago

Hi @Deepcuts

This is an issue with the Debian packaging. The node binary is named nodejs, aprogram was already named node in their repos.

A temporary fix would be ln -s /usr/bin/nodejs /usr/bin/node, but make sure to remove that binary after your done. You could create that link anywhere in your path, but since your running as root I don't think the default Debian bash adds ~/bin to your bath.

Lastly, you don't even have to build if you are not developing. web/bundle.js is already in the repository so you can just host that and be done!

Feel free to grab me on IRC, I will be on all night working. thanks

Sean-Der commented 9 years ago

Hi @Deepcuts

I am going to close this for inactivity. If this is still not working for you, please reopen!