Open itguy51 opened 12 years ago
+1
I have the same issue on debian 6.
Here is my log file :
1295 error error rolling back Error: ENOTEMPTY, rmdir '/usr/local/lib/node_modules/sm/node_modules/sourcemint-pm-sm/node_modules/sourcemint-pm-tar/node_modules/tar' 1295 error error rolling back tar@0.1.13 { [Error: ENOTEMPTY, rmdir '/usr/local/lib/node_modules/sm/node_modules/sourcemint-pm-sm/node_modules/sourcemint-pm-tar/node_modules/tar'] 1295 error error rolling back errno: 53, 1295 error error rolling back code: 'ENOTEMPTY', 1295 error error rolling back path: '/usr/local/lib/node_modules/sm/node_modules/sourcemint-pm-sm/node_modules/sourcemint-pm-tar/node_modules/tar' } 1342 error Error: ENOENT, chown '/usr/local/lib/node_modules/sm/node_modules/sourcemint-pm-sm/node_modules/sourcemint-pm-tar/node_modules/tar/node_modules/fstream/lib/socket-reader.js' 1342 error { [Error: ENOENT, chown '/usr/local/lib/node_modules/sm/node_modules/sourcemint-pm-sm/node_modules/sourcemint-pm-tar/node_modules/tar/node_modules/fstream/lib/socket-reader.js'] 1342 error errno: 34, 1342 error code: 'ENOENT', 1342 error path: '/usr/local/lib/node_modules/sm/node_modules/sourcemint-pm-sm/node_modules/sourcemint-pm-tar/node_modules/tar/node_modules/fstream/lib/socket-reader.js', 1342 error fstream_finish_call: 'chown', 1342 error fstream_type: 'File', 1342 error fstream_path: '/usr/local/lib/node_modules/sm/node_modules/sourcemint-pm-sm/node_modules/sourcemint-pm-tar/node_modules/tar/node_modules/fstream/lib/socket-reader.js', 1342 error fstream_class: 'FileWriter', 1342 error fstream_stack: 1342 error [ 'Writer._finish (/usr/local/lib/node_modules/npm/node_modules/fstream/lib/writer.js:305:19)', 1342 error '/usr/local/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:230:7', 1342 error 'Object.oncomplete (fs.js:297:15)' ] } 1343 error You may report this log at: 1343 error http://github.com/isaacs/npm/issues 1343 error or email it to: 1343 error npm-@googlegroups.com 1344 error System Linux 2.6.32-5-amd64 1345 error command "node" "/usr/local/bin/npm" "install" "-g" "sm" 1346 error cwd /home/victor 1347 error node -v v0.8.0-pre 1348 error npm -v 1.1.30 1349 error path /usr/local/lib/node_modules/sm/node_modules/sourcemint-pm-sm/node_modules/sourcemint-pm-tar/node_modules/tar/node_modules/fstream/lib/socket-reader.js 1350 error fstream_path /usr/local/lib/node_modules/sm/node_modules/sourcemint-pm-sm/node_modules/sourcemint-pm-tar/node_modules/tar/node_modules/fstream/lib/socket-reader.js 1351 error fstream_type File 1352 error fstream_class FileWriter 1353 error fstream_finish_call chown 1354 error code ENOENT 1355 error message ENOENT, chown '/usr/local/lib/node_modules/sm/node_modules/sourcemint-pm-sm/node_modules/sourcemint-pm-tar/node_modules/tar/node_modules/fstream/lib/socket-reader.js' 1356 error errno 34 1357 error fstream_stack Writer._finish (/usr/local/lib/node_modules/npm/node_modules/fstream/lib/writer.js:305:19) 1357 error fstream_stack /usr/local/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:230:7 1357 error fstream_stack Object.oncomplete (fs.js:297:15) 1358 error 34 errno
same here but I'm using debian
This looks like an issue with the way NPM installs binaries onto the PATH.
I'll have to revisit that and not use NPM to put sm
onto the path.
+1
when is this going to be fixed?
It appears not to be as much an issue with npm, but with Node itself, After some checking, I decided to not use a pre-compiled version, but to try and compile it myself. This is working fine right now, However, I would consider not using a pre-compiled one if you can spare the time to build one yourself.
+1 Can't run sm from command line after installing
+1 ubuntu i386 12.04, npm 1.1.24, node v0.6.19
@itguy51 Is correct...it's a problem with the precompiled apt packages. Follow the node Ubuntu install instructions on nodejs.org and add the 'unofficial' repository, and reinstall.
I try install on Ubuantu 10.04 server, very well.
2012/10/7 Nick Daugherty notifications@github.com
@itguy51 https://github.com/itguy51 Is correct...it's a problem with the precompiled apt packages. Follow the node Ubuntu install instructions on node.js and add the 'unofficial' repository, and reinstall.
— Reply to this email directly or view it on GitHubhttps://github.com/sourcemint/sm-npm/issues/8#issuecomment-9204984.
Following the suggestion by @nickdaugherty - Use the http://apptob.org/ tool to simplify installation.
I have the same issue running Ubuntu on Amazon EC2.
"sm" is a different tool on Ubuntu. Plus, I don't see why I should have to install SM (or any other node.js app/package) as root - I don't want it muddying my OS thank you very much. npm install works for other packages, why not sm?
@whodafly Hmm, I did a search on sm
and did not come up with any existing tools. Can you send me a link to that project?
The current install tries to put the sm
command on the PATH
. The next release will fail silently if that fails and will show you a command to run to add it yourself.
@:~$ apt-cache show sm Package: sm Priority: optional Section: universe/games Installed-Size: 128 Maintainer: Ubuntu Developers Original-Maintainer: Joachim Breitner Architecture: amd64 Source: screen-message Version: 0.19-1 Depends: libatk1.0-0 (>= 1.29.3), libc6 (>= 2.4), libcairo2 (>= 1.2.4), libfontconfig1 (>= 2.8.0), libfreetype6 (>= 2.2.1), libglib2.0-0 (>= 2.16.0), libgtk2.0-0 (>= 2.18.0), libpango1.0-0 (>= 1.14.0) Filename: pool/universe/s/screen-message/sm_0.19-1_amd64.deb Size: 16866 MD5sum: 8edfc305ca094c4036e495295214432b SHA1: 656e6a40f3fdaa9432bbd896f0a0a41d9a9a6228 SHA256: c32dc2b0a4c5c74c4f8aa0fb1742b4aeac4367ca5aaa6f21b1f34747a6284bb1 Description-en: Displays a short text fullscreen Screen Message will display a given multi-line message as large as possible, fullscreen and black on white. You can specify the text either when launching sm, or edit it while the program is running. . It is useful to send messages across a room, e.g. during an university lecture. For fast startup, it is recommended to bind it to a key in your Desktop Environment. Description-md5: 91fe8f689d157fbba591713d7e201f4d Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu
I'm running Ubuntu (well, Kubuntu) 12.10.
@whodafly Ah, of course. I heard of that feature in the past.
I still want to call the sourcemint command-line tool sm
as it is short and the audiences of the two tools seem to be somewhat separate.
So, say you want to use sourcemint and install it under a different command. Would you just do npm install -g sm
and then see a message that includes the command you need to link to your PATH
?
What would you call it?
I'm primarily a Python developer, and I use virtualenv a lot, so being able to "install" something locally into a directory works perfectly well for me. If I'm deploying something to a production server, I don't necessarily want to install it as root either.
So, as long as I can type "./sm" I'm perfectly happy. I'm also happy with "./sourcemint" as I would just tab-complete it anyway :-)
Since 0.3 is taking longer than I had hoped I have made a hotfix to try and resolve this issue.
Please try sm@0.2.12-rc.1
. This will warn you if sm
could not be linked into your PATH but will not fail anymore.
Please let me know if this resolves your issue for now.
I am trying to install this package, but it does not work under Ubuntu 12.04, as it never installs the binary via NPM. I will type 'npm install -g sm', and it throws a bunch of access errors, while a 'sudo npm install -g sm' works fine, however, when typing 'sm -h' into the console, I get 'The program 'sm' is currently not installed. You can install it by typing: sudo apt-get install sm', which is not the proper application.