Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

npm 0.3.2 has broken install of hashlib - 0.3.0 worked. #621

Closed
wbecker opened this Issue Feb 19, 2011 · 4 comments

Comments

Projects
None yet
2 participants

wbecker commented Feb 19, 2011

I installed hashlib yesterday and it worked fine, but I tried it on a new computer today and it didn't work. The only thing that has changed is the version of npm (even the hash of the install of hashlib is the same!). It looks like it doesn't like the trailing comma in the contributors array. I've asked hashlib to fix this up as well (brainfucker/hashlib#11)

0.3.0 working:

npm info it worked if it ends with ok
npm info using npm@0.3.0-6
npm info using node@v0.4.0
npm info fetch http://registry.npmjs.org/hashlib/-/hashlib-1.0.0.tgz
npm info calculating sha1 /tmp/npm-1298056121295/1298056121295-0.5797675373032689/tmp.tgz
npm info shasum 42d6d331a49966e8a70c4199b773d21d7c953f25
npm info calculating sha1 /usr/lib/node/.npm/.cache/hashlib/1.0.0/package.tgz
npm info shasum 3d59ab019fed81f8ae057d9c7d5b515a20e3e553
npm info preinstall hashlib@1.0.0
Nothing to clean (project not configured)
Checking for program g++ or c++ : /usr/bin/g++
Checking for program cpp : /usr/bin/cpp
Checking for program ar : /usr/bin/ar
Checking for program ranlib : /usr/bin/ranlib
Checking for g++ : ok
Checking for program gcc or cc : /usr/bin/gcc
Checking for program ar : /usr/bin/ar
Checking for program ranlib : /usr/bin/ranlib
Checking for gcc : ok
Checking for node path : not found
Checking for node prefix : ok /usr
'configure' finished successfully (0.250s)
Waf: Entering directory /usr/lib64/node/.npm/hashlib/1.0.0/package/build' [1/6] cc: libhash/md4c.c -> build/default/libhash/md4c_1.o [2/6] cc: libhash/md5c.c -> build/default/libhash/md5c_1.o [3/6] cc: libhash/sha0c.c -> build/default/libhash/sha0c_1.o [4/6] cxx: hashlib.cc -> build/default/hashlib_2.o [5/6] cxx_link: build/default/hashlib_2.o build/default/libhash/md4c_1.o build/default/libhash/md5c_1.o build/default/libhash/sha0c_1.o -> build/default/hashlib.node [6/6] cc_link: build/default/libhash/md4c_1.o build/default/libhash/md5c_1.o build/default/libhash/sha0c_1.o -> build/default/liblibhash.so Waf: Leaving directory/usr/lib64/node/.npm/hashlib/1.0.0/package/build'
'build' finished successfully (3.443s)
npm info install hashlib@1.0.0
npm info postinstall hashlib@1.0.0
npm info preactivate hashlib@1.0.0
npm info activate hashlib@1.0.0
npm info postactivate hashlib@1.0.0
npm info build Success: hashlib@1.0.0
npm ok

0.3.2 not working:

npm info it worked if it ends with ok
npm info using npm@0.3.2
npm info using node@v0.4.0
npm info fetch http://registry.npmjs.org/hashlib/-/hashlib-1.0.0.tgz
npm info calculating sha1 /tmp/npm-1298155154217/1298155154217-0.015293280128389597/tmp.tgz
npm info shasum 42d6d331a49966e8a70c4199b773d21d7c953f25
npm ERR! couldn't read package.json in /tmp/npm-1298155154217/1298155154217-0.015293280128389597/contents/package
npm ERR! Error installing hashlib@1.0.0
npm ERR! Error: Failed to parse json
npm ERR! Unexpected token ]
npm ERR! {
npm ERR! "name": "hashlib",
npm ERR! "author": "Illarionov Oleg",
npm ERR! "description": "lib for node which makes hashes",
npm ERR! "version": "1.0.0",
npm ERR! "contributors": [
npm ERR! { "name": "Fedor Indutny", "email": "fedor.indutny@gmail.com" },
npm ERR! { "name": "Seth Fitzsimmons", "email": "seth@mojodna.net" },
npm ERR! { "name": "Wade Simmons", "email": "wade@wades.im" },
npm ERR! ],
npm ERR! "main": "./build/default/hashlib.node",
npm ERR! "directories": { "lib": "./build/default" },
npm ERR! "engines": { "node": ">= 0.2.0" }
npm ERR! }
npm ERR!
npm ERR! at /usr/lib/node/.npm/npm/0.3.2/package/lib/utils/read-json.js:73:13
npm ERR! at P (/usr/lib/node/.npm/npm/0.3.2/package/lib/utils/read-json.js:62:40)
npm ERR! at cb (/usr/lib/node/.npm/npm/0.3.2/package/lib/utils/graceful-fs.js:31:9)
npm ERR! at [object Object]. (fs.js:86:5)
npm ERR! at [object Object].emit (events.js:39:17)
npm ERR! at afterRead (fs.js:840:12)
npm ERR! Report this entire log at http://github.com/isaacs/npm/issues
npm ERR! or email it to npm-@googlegroups.com
npm ERR! Just tweeting a tiny part of the error will not be helpful.
npm not ok

Owner

isaacs commented Feb 19, 2011

npm requires proper json now.

wbecker commented Feb 19, 2011

So it seems! Is there any quick way of getting this working, or do I have to wait until hashlib fix it up at their end?

Owner

isaacs commented Feb 19, 2011

Get hashlib to update their end. A github pull request usually speeds the process along :)

wbecker commented Feb 19, 2011

Thanks, done that now. Hopefully it all flows through quickly!

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment