-
Notifications
You must be signed in to change notification settings - Fork 7.3k
Official Linux binary for npm does not work #6292
Comments
Sorry, my server is: Ubuntu 10.04.4 LTS |
lLnk to http://nodejs.org/download/ and add a short primer on how to extract the tarballs. Fixes #6292.
I would chalk that down as a case of mismatched expectations but at any rate, I've added a note to the README in b7f36e1. Cheers. |
Thanks. Scratching my head as to how my commands were not equivalent, apart from dtrace and the manpages, which shouldn't have been crucial as far as I can tell. (I tried your instructions on new ubuntu VMs with both /usr/local and /usr and they work fine both ways.) Is the script that builds these binary tarballs in github somewhere? I'd like to take a stab at support for "make install" just doing the sensible thing (/usr/local). |
Well, |
There is no Makefile in the tarball you get when you download binaries. root@tom-ubuntu-11:/usr/local/src# tar -zxf Am I missing something? It wouldn't surprise me if I were... On Tue, Oct 1, 2013 at 2:40 AM, Ben Noordhuis notifications@github.comwrote:
Tom Boutell |
To be clear, I am talking about improving the experience for those who On Tue, Oct 1, 2013 at 10:37 AM, Tom Boutell tom@punkave.com wrote:
Tom Boutell |
Oh, is that what you mean. I don't consider the current tarball packaging to be particularly broken. I gauge brokenness by the number of bug reports and this is literally the first time someone reported an issue. :-) |
Stack Overflow threads about the binary installation issue seem to peter Your addition to the README helps, thank you. On Tue, Oct 1, 2013 at 10:48 AM, Ben Noordhuis notifications@github.comwrote:
Tom Boutell |
Guys i need help here am so stranded now!! How can i deplay the app drive-grease@drivegrease-HP-630-Notebook-PC:~/Desktop/coursework$ heroku git:remote -app findalawyer Help topics, type "heroku help TOPIC" for more details: heroku version # print the version |
@Boniface22 please try the mailing list or Stack Overflow. The issue tracker is for reporting bugs in Node core. |
@Boniface22 you've been told once already: issues on this github repository are for bugs in the core of node, not for Heroku deployment tips. This problem has nothing to do with the core of node. Go research your problem on stackoverflow, Heroku's website, etc. You will not be answered here. |
The official Linux binaries arrive in a tarfile with a bin/ subdirectory. The README does not cover installation and there is no script for that purpose, so what comes next is an educated guess:
After doing this, "node" works fine, but "npm" always fails with the same error:
Note that npmlog does exist in /usr/lib/node_modules/npm/node_modules/npmlog.
There are references to the issue in stackoverflow, which everyone eventually resolves by installing from source. That worked for us too, but having broken npm binaries available on nodejs.org seems worse than having no binaries at all in terms of sharing the glory of node with the masses.
Thanks!
The text was updated successfully, but these errors were encountered: