More dependency problems #1797

Closed
zencuke opened this Issue Nov 27, 2011 · 5 comments

Comments

Projects
None yet
2 participants

zencuke commented Nov 27, 2011

Yes I am on a Mac as I reported earlier.

So I deleted the fink hierarchy and took /sw/bin out of my path. That allowed got npm to install again but now I have problems installing Locker.

papas-macintosh:Locker steven$ npm install
npm WARN async@0.1.9 package.json: bugs['web'] should probably be bugs['url']
npm WARN htmlparser2@1.0.0 package.json: bugs['web'] should probably be bugs['url']
npm WARN mongodb@0.9.6-15 package.json: bugs['web'] should probably be bugs['url']
npm WARN request@2.1.1 package.json: bugs['web'] should probably be bugs['url']
npm WARN wrench@1.1.0 package.json: bugs['web'] should probably be bugs['url']
npm WARN xmlbuilder@0.1.2 package.json: bugs['web'] should probably be bugs['url']
npm ERR! error installing unshortener@0.0.8 Error: version not found: 1.0.1 : bitly/1.0.1
npm ERR! error installing unshortener@0.0.8 at Request._callback (/usr/local/lib/node_modules/npm/lib/utils/npm-registry-client/request.js:180:12)
npm ERR! error installing unshortener@0.0.8 at Request.callback (/usr/local/lib/node_modules/npm/node_modules/request/main.js:99:22)
npm ERR! error installing unshortener@0.0.8 at Request. (/usr/local/lib/node_modules/npm/node_modules/request/main.js:361:18)
npm ERR! error installing unshortener@0.0.8 at Request.emit (events.js:64:17)
npm ERR! error installing unshortener@0.0.8 at IncomingMessage. (/usr/local/lib/node_modules/npm/node_modules/request/main.js:327:16)
npm ERR! error installing unshortener@0.0.8 at IncomingMessage.emit (events.js:81:20)
npm ERR! error installing unshortener@0.0.8 at HTTPParser.onMessageComplete (http.js:133:23)
npm ERR! error installing unshortener@0.0.8 at CleartextStream.ondata (http.js:1227:22)
npm ERR! error installing unshortener@0.0.8 at CleartextStream._push (tls.js:303:27)
npm ERR! error installing unshortener@0.0.8 at SecurePair.cycle (tls.js:574:20)
npm ERR! Error: version not found: 1.0.1 : bitly/1.0.1
npm ERR! at Request._callback (/usr/local/lib/node_modules/npm/lib/utils/npm-registry-client/request.js:180:12)
npm ERR! at Request.callback (/usr/local/lib/node_modules/npm/node_modules/request/main.js:99:22)
npm ERR! at Request. (/usr/local/lib/node_modules/npm/node_modules/request/main.js:361:18)
npm ERR! at Request.emit (events.js:64:17)
npm ERR! at IncomingMessage. (/usr/local/lib/node_modules/npm/node_modules/request/main.js:327:16)
npm ERR! at IncomingMessage.emit (events.js:81:20)
npm ERR! at HTTPParser.onMessageComplete (http.js:133:23)
npm ERR! at CleartextStream.ondata (http.js:1227:22)
npm ERR! at CleartextStream._push (tls.js:303:27)
npm ERR! at SecurePair.cycle (tls.js:574:20)
npm ERR! Report this entire log at:
npm ERR! http://github.com/isaacs/npm/issues
npm ERR! or email it to:
npm ERR! npm-@googlegroups.com
npm ERR!
npm ERR! System Darwin 11.2.0
npm ERR! command "node" "/usr/local/bin/npm" "install"
npm ERR! cwd /Users/steven/Locker
npm ERR! node -v v0.4.9
npm ERR! npm -v 1.0.106
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /Users/steven/Locker/npm-debug.log
npm not ok

zencuke commented Nov 28, 2011

The lockerProject took out the dependency for unshortener because it is not used anymore. Unfortunately now npm install fails when trying to install CLucene. npm reports this as a problem with CLucene. Should I track down the CLucene web site and move this problem report there? I suspect this is related to the recent Macintosh xCode upgrade which changes the version of gcc4.2 which is installed by default. It is now the llvm version. That change has apparently broken a bunch of open source tools and apps on the Macintosh. Maybe it is time for me to get Windows working in a VM on my Mac ;-(. Is it npm or the package script that is responsible for choosing which gcc version to use to build the package? In general what is the split between responsibilities between npm and the package specific scripts? Is it possible to extract what npm does so I can test the CLucene build without npm? Who maintains the clucene package interface to npm? Sorry for all the pestering questions. The nice thing about a package manager is that it hides all those nitty gritty details about dependencies etc. The bad thing about package managers is that it hides the nitty grity details needed to debug problems when installs don't work.

Here npm error log.

Checking for library clucene-core : 'configure' finished successfully (0.497s)
Waf: Entering directory /Users/steven/Locker/node_modules/daemon/build' [1/2] cxx: src/daemon.cc -> build/Release/src/daemon_1.o yes 'configure' finished successfully (2.238s) Waf: Entering directory/Users/steven/Locker/node_modules/clucene/build'
[1/2] cxx: src/clucene_bindings.cpp -> build/Release/src/clucene_bindings_1.o
[2/2] cxx_link: build/Release/src/daemon_1.o -> build/Release/daemon.node
Waf: Leaving directory /Users/steven/Locker/node_modules/daemon/build' 'build' finished successfully (2.882s) ../src/clucene_bindings.cpp: In static member function ‘static v8::Handle<v8::Value> Lucene::AddDocumentAsync(const v8::Arguments&)’: ../src/clucene_bindings.cpp:286: error: invalid conversion from ‘int (*)(eio_req*)’ to ‘void (*)(eio_req*)’ ../src/clucene_bindings.cpp:286: error: initializing argument 1 of ‘eio_req* eio_custom(void (*)(eio_req*), int, int (*)(eio_req*), void*)’ ../src/clucene_bindings.cpp: In static member function ‘static v8::Handle<v8::Value> Lucene::DeleteDocumentAsync(const v8::Arguments&)’: ../src/clucene_bindings.cpp:431: error: invalid conversion from ‘int (*)(eio_req*)’ to ‘void (*)(eio_req*)’ ../src/clucene_bindings.cpp:431: error: initializing argument 1 of ‘eio_req* eio_custom(void (*)(eio_req*), int, int (*)(eio_req*), void*)’ ../src/clucene_bindings.cpp: In static member function ‘static v8::Handle<v8::Value> Lucene::DeleteDocumentsByTypeAsync(const v8::Arguments&)’: ../src/clucene_bindings.cpp:530: error: invalid conversion from ‘int (*)(eio_req*)’ to ‘void (*)(eio_req*)’ ../src/clucene_bindings.cpp:530: error: initializing argument 1 of ‘eio_req* eio_custom(void (*)(eio_req*), int, int (*)(eio_req*), void*)’ ../src/clucene_bindings.cpp: In static member function ‘static v8::Handle<v8::Value> Lucene::SearchAsync(const v8::Arguments&)’: ../src/clucene_bindings.cpp:642: error: invalid conversion from ‘int (*)(eio_req*)’ to ‘void (*)(eio_req*)’ ../src/clucene_bindings.cpp:642: error: initializing argument 1 of ‘eio_req* eio_custom(void (*)(eio_req*), int, int (*)(eio_req*), void*)’ ../src/clucene_bindings.cpp: In static member function ‘static v8::Handle<v8::Value> Lucene::OptimizeAsync(const v8::Arguments&)’: ../src/clucene_bindings.cpp:774: error: invalid conversion from ‘int (*)(eio_req*)’ to ‘void (*)(eio_req*)’ ../src/clucene_bindings.cpp:774: error: initializing argument 1 of ‘eio_req* eio_custom(void (*)(eio_req*), int, int (*)(eio_req*), void*)’ Waf: Leaving directory/Users/steven/Locker/node_modules/clucene/build'
Build failed: -> task failed (err #1):
{task: cxx clucene_bindings.cpp -> clucene_bindings_1.o}
npm ERR! error installing clucene@0.2.3 Error: clucene@0.2.3 install: node-waf configure build
npm ERR! error installing clucene@0.2.3 sh "-c" "node-waf configure build" failed with 1
npm ERR! error installing clucene@0.2.3 at ChildProcess. (/usr/local/lib/node_modules/npm/lib/utils/exec.js:49:20)
npm ERR! error installing clucene@0.2.3 at ChildProcess.emit (events.js:67:17)
npm ERR! error installing clucene@0.2.3 at ChildProcess.onexit (child_process.js:192:12)
npm ERR! clucene@0.2.3 install: node-waf configure build
npm ERR! sh "-c" "node-waf configure build" failed with 1
npm ERR!
npm ERR! Failed at the clucene@0.2.3 install script.
npm ERR! This is most likely a problem with the clucene package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-waf configure build
npm ERR! You can get their info via:
npm ERR! npm owner ls clucene
npm ERR! There is likely additional logging output above.
npm ERR!
npm ERR! System Darwin 11.2.0
npm ERR! command "node" "/usr/local/bin/npm" "install"
npm ERR! cwd /Users/steven/Locker
npm ERR! node -v v0.4.9
npm ERR! npm -v 1.0.106
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /Users/steven/Locker/npm-debug.log
npm not ok

Owner

isaacs commented Nov 28, 2011

The error message is trying to tell you what's wrong.


npm ERR! Failed at the clucene@0.2.3 install script.
npm ERR! This is most likely a problem with the clucene package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-waf configure build
npm ERR! You can get their info via:
npm ERR! npm owner ls clucene
npm ERR! There is likely additional logging output above.

@isaacs isaacs closed this Nov 28, 2011

zencuke commented Nov 28, 2011

I think I said that in my comment. I was asking for additional information.
I'm really not trying to be a pain. I did read the error message carefully
before I commented. You seem to be suggesting I missed it. Sometimes
messages like this are right and sometimes they misdiagnose. It is hard to
guess which if you don't have experience working with the developers. As an
innocent bystander who never heard of node or npm before a couple of days
ago I'm just trying to understand enough details to hopefully give me a
little more leverage when I go to the CLucene maintainers. I have spent a
lot of time trying to debug this series of issues. I am not asking
questions because I am too lazy to do the footwork and want you to do it
for me. There are three development teams here: npm, the lockerProject that
created the package.json file and the CLucene team. It is easy for the end
user to get lost in finger pointing between teams like these.

On Mon, Nov 28, 2011 at 12:01 PM, Isaac Z. Schlueter wrote:

The error message is trying to tell you what's wrong.


npm ERR! Failed at the clucene@0.2.3 install script.
npm ERR! This is most likely a problem with the clucene package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-waf configure build
npm ERR! You can get their info via:
npm ERR! npm owner ls clucene
npm ERR! There is likely additional logging output above.

Reply to this email directly or view it on GitHub:
isaacs#1797 (comment)

Owner

isaacs commented Nov 28, 2011

Sorry, I didn't mean to imply that you hadn't investigated. You just asked a lot of questions in your post, and I don't really have the answer to most of them.

npm is doing what it's told. The lockerProject package said that it needs CLucene. So, it goes out and fetches CLucene. The CLucene package says, "Run this command: node-waf configure build", so npm does it. When it does that, the command responds with a non-zero error code, indicating that it failed. So, npm says, "CLucene told me to do this thing, and I tried to do it, but it failed, so I'm exiting like I'm supposed to."

This is the first time I've ever seen the CLucene build output, or even heard of this package. But, from the output, my best guess would be that error: invalid conversion from ‘int (*)(eio_req*)’ to ‘void (*)(eio_req*)’ is indicating a package that was developed for node 0.4 and can't compile against node 0.6.

If the CLucene package had an "engines":{ "node": "0.4" } statement, then npm would have known this failure ahead of time, and told you that it could not find a suitable version prior to running the build command.

Try emailing erictj, or posting a bug.

$ npm owner ls clucene
erictj <ericj@loopshot.com>

$ npm view clucene bugs.url
http://github.com/erictj/node-clucene/issues

zencuke commented Nov 28, 2011

Isaac,

Thanks. I was fishing for just this kind of information. I'm frankly more
suspicious of the lockerProject dependencies because they have changed a
bunch of them recently (last couple of days) and I don't think changes to
that project get much testing, especially from a clean workstation. They
seem to be in early beta release mode. Their blog doesn't mention version
numbers. When you download you seem to get the latest development release.
I don't want to pester the clucene maintainer if it is really a
lockerProject problem so I'm trying to get a handle on what lockerProject
might have done to confuse the clucene install. I'm not at my machine but
I'm pretty sure locker requires node 0.4 so it is possible there are some
cross dependency problems. And always the big recent change in gcc version
on the Macintosh lurks as a possible culprit.

Anyway the node compatibility question gives me something to look for.
Thanks again.

-steve

On Mon, Nov 28, 2011 at 2:28 PM, Isaac Z. Schlueter <
reply@reply.github.com

wrote:

Sorry, I didn't mean to imply that you hadn't investigated. You just
asked a lot of questions in your post, and I don't really have the answer
to most of them.

npm is doing what it's told. The lockerProject package said that it needs
CLucene. So, it goes out and fetches CLucene. The CLucene package says,
"Run this command: node-waf configure build", so npm does it. When it
does that, the command responds with a non-zero error code, indicating that
it failed. So, npm says, "CLucene told me to do this thing, and I tried to
do it, but it failed, so I'm exiting like I'm supposed to."

This is the first time I've ever seen the CLucene build output, or even
heard of this package. But, from the output, my best guess would be that
error: invalid conversion from int (*)(eio_req*) to void (*)(eio_req*) is indicating a package that was developed for node 0.4 and
can't compile against node 0.6.

If the CLucene package had an "engines":{ "node": "0.4" } statement,
then npm would have known this failure ahead of time, and told you that it
could not find a suitable version prior to running the build command.

Try emailing erictj, or posting a bug.

$ npm owner ls clucene
erictj <ericj@loopshot.com>

$ npm view clucene bugs.url
http://github.com/erictj/node-clucene/issues

Reply to this email directly or view it on GitHub:
isaacs#1797 (comment)

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