NPM: docpad 6.26 seems to fail to install, maybe because of coffee 1.6?

quesada commented 11 years ago

balupton commented 11 years ago

Hey mate, can you provide the rest of the details that are asked for with bug reports. You can find the list here - https://github.com/bevry/docpad/blob/master/CONTRIBUTING.md#support - it should show up as a banner when you file a new issue. Thanks mate, it'll really help tracking this down.

quesada commented 11 years ago

docpad --version I cannot provide because I cannot get a running docpad.

Some of the info was already on the log:

npm ERR! System Linux 3.5.0-25-lowlatency npm ERR! command "nodejs" "/usr/bin/npm" "install" "-fg" "docpad" npm ERR! cwd /home/jack/Copy/sites npm ERR! node -v v0.8.14 npm ERR! npm -v 1.1.65

uname -a Linux hpappy 3.5.0-25-lowlatency #25-Ubuntu SMP PREEMPT Tue Feb 26 09:53:37 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

ubuntu 12.10

What you did: tried to install docpad, first locally, then globally (with sudo) following the instructions

What happened: error log. I've been debugging for a while now, so the latest error log seems to blame a package called joe:

ws@0.4.25 install /home/jack/Copy/sites/josequesada.docpad/node_modules/docpad-plugin-livereload/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws (node-gyp rebuild 2> builderror.log) || (exit 0)

make: Entering directory /home/jack/Copy/sites/josequesada.docpad/node_modules/docpad-plugin-livereload/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws/build' CXX(target) Release/obj.target/bufferutil/src/bufferutil.o SOLINK_MODULE(target) Release/obj.target/bufferutil.node SOLINK_MODULE(target) Release/obj.target/bufferutil.node: Finished COPY Release/bufferutil.node CXX(target) Release/obj.target/validation/src/validation.o SOLINK_MODULE(target) Release/obj.target/validation.node SOLINK_MODULE(target) Release/obj.target/validation.node: Finished COPY Release/validation.node make: Leaving directory/home/jack/Copy/sites/josequesada.docpad/node_modules/docpad-plugin-livereload/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws/build' npm http GET https://registry.npmjs.org/keypress npm http GET https://registry.npmjs.org/cli-color npm http GET https://registry.npmjs.org/underscore npm http GET https://registry.npmjs.org/request/2.9.202 npm http GET https://registry.npmjs.org/xmlbuilder/0.1.5 npm http GET https://registry.npmjs.org/connect/2.7.2 npm http GET https://registry.npmjs.org/commander/0.6.1 npm http GET https://registry.npmjs.org/joe npm http GET https://registry.npmjs.org/stack-trace/0.0.5 npm http GET https://registry.npmjs.org/range-parser/0.0.4 npm http GET https://registry.npmjs.org/coffee-script npm http GET https://registry.npmjs.org/hashish/0.0.4 npm http GET https://registry.npmjs.org/mkdirp/0.3.3 npm http GET https://registry.npmjs.org/js2coffee npm http GET https://registry.npmjs.org/cookie/0.0.5 npm http GET https://registry.npmjs.org/buffer-crc32/0.1.1 npm http GET https://registry.npmjs.org/fresh/0.1.0 npm http GET https://registry.npmjs.org/methods/0.0.1 npm http GET https://registry.npmjs.org/send/0.1.0 npm http GET https://registry.npmjs.org/cookie-signature/0.0.1 npm http GET https://registry.npmjs.org/debug npm http GET https://registry.npmjs.org/argparse npm http GET https://registry.npmjs.org/glob npm http 304 https://registry.npmjs.org/xmlbuilder/0.1.5 npm http GET https://registry.npmjs.org/xmlbuilder/-/xmlbuilder-0.1.5.tgz npm http 304 https://registry.npmjs.org/connect/2.7.2 npm http GET https://registry.npmjs.org/connect/-/connect-2.7.2.tgz npm http 304 https://registry.npmjs.org/commander/0.6.1 npm http GET https://registry.npmjs.org/commander/-/commander-0.6.1.tgz npm http 304 https://registry.npmjs.org/joe npm ERR! Error: No compatible version found: joe@'joe@~1.1.0' npm ERR! Valid install targets: npm ERR! ["0.1.0","0.2.0","0.2.1","0.3.0","0.3.1","0.3.2","0.3.3","0.3.4","0.4.0","1.0.0","1.0.1","1.0.2","1.0.3","1.1.0","1.1.1","1.1.2"] npm ERR! at installTargetsError (/usr/lib/nodejs/npm/lib/cache.js:563:10) npm ERR! at /usr/lib/nodejs/npm/lib/cache.js:478:10 npm ERR! at saved (/usr/lib/nodejs/npm/node_modules/npm-registry-client/lib/get.js:138:7) npm ERR! at /usr/lib/nodejs/npm/node_modules/graceful-fs/graceful-fs.js:218:7 npm ERR! at Object.oncomplete (fs.js:297:15) npm ERR! If you need help, you may report this log at: npm ERR! http://github.com/isaacs/npm/issues npm ERR! or email it to: npm ERR! npm-@googlegroups.com

npm ERR! System Linux 3.5.0-25-lowlatency npm ERR! command "nodejs" "/usr/bin/npm" "install" "-f" npm ERR! cwd /home/jack/Copy/sites/josequesada.docpad npm ERR! node -v v0.8.14 npm ERR! npm -v 1.1.65 npm ERR! Error: ENOENT, lstat '/home/jack/Copy/sites/josequesada.docpad/node_modules/docpad/node_modules/iconv/deps/libiconv/lib/translit.def' npm ERR! If you need help, you may report this log at: npm ERR! http://github.com/isaacs/npm/issues npm ERR! or email it to: npm ERR! npm-@googlegroups.com

What you expected a working install of docpad

Didn't see any popup with bug report instructions though.

balupton commented 11 years ago

That's is strange... Can you try upgrade your npm version, npm install -g npm, then try again - we now recommend upgrading npm as part of the docpad install instructions, as a few times installation problems are due to outdated npm versions (latest is v1.2.5 I believe).

We also have a known issue with iconv failing to install on some systems, we're working on fixing that now.

quesada commented 11 years ago

sudo npm install -g npm

npm http GET https://registry.npmjs.org/npm npm http 304 https://registry.npmjs.org/npm npm ERR! error rolling back Error: Refusing to delete: /usr/bin/npm not in /usr/lib/node_modules/npm npm ERR! error rolling back at clobberFail (/usr/lib/nodejs/npm/lib/utils/gently-rm.js:41:12) npm ERR! error rolling back at next (/usr/lib/nodejs/npm/lib/utils/gently-rm.js:27:14) npm ERR! error rolling back at /usr/lib/nodejs/npm/lib/utils/gently-rm.js:36:12 npm ERR! error rolling back at Object.oncomplete (fs.js:297:15) npm ERR! error rolling back npm@1.2.15 { [Error: Refusing to delete: /usr/bin/npm not in /usr/lib/node_modules/npm] code: 'EEXIST', path: '/usr/bin/npm' } npm ERR! Refusing to delete: /usr/bin/npm not in /usr/lib/node_modules/npm File exists: /usr/bin/npm Move it away, and try again.

npm ERR! System Linux 3.5.0-25-lowlatency npm ERR! command "nodejs" "/usr/bin/npm" "install" "-g" "npm" npm ERR! cwd /home/jack/Copy/sites/josequesada.docpad npm ERR! node -v v0.8.14 npm ERR! npm -v 1.1.65 npm ERR! path /usr/bin/npm npm ERR! code EEXIST npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /home/jack/Copy/sites/josequesada.docpad/npm-debug.log npm ERR! not ok code 0

- Jose

http://josequesada.com @quesada

On Mon, Mar 25, 2013 at 1:11 AM, Benjamin Arthur Lupton < notifications@github.com> wrote:

That's is strange... Can you try upgrade your npm version, npm install -g npm, then try again - we now recommend upgrading npm as part of the docpad install instructions http://docpad.org/install, as a few times installation problems are due to outdated npm versions (latest is v1.2.5 I believe)

— Reply to this email directly or view it on GitHubhttps://github.com/bevry/docpad/issues/470#issuecomment-15372758 .

balupton commented 11 years ago

Unfortunately, that's a bug for NPM. I can't help you there.

quesada commented 11 years ago

wow. I'm effectively stuck... I cannot change my site, which is my source of income, with docpad. I'm starting to realize how dangerous it is to bet the farm on bleeding edge technology (node).

Thankfully, this is an static site, so I can just manually handcode my changes. If it was a dynamic site (like wordpress) I'd be seriously FUBARed.

What is the bug exactly? Is it reported? Are these bugs routinely fixed?

Thanks for your help. I'll reconsider my strategy once I get out of this mess.

- Jose

http://josequesada.com @quesada

On Mon, Mar 25, 2013 at 1:52 AM, Benjamin Arthur Lupton < notifications@github.com> wrote:

Unfortunately, that's a bug for NPM. I can't help you there.

— Reply to this email directly or view it on GitHubhttps://github.com/bevry/docpad/issues/470#issuecomment-15373456 .

balupton commented 11 years ago

I can understand your frustration, it is really really frustrating when things you depend on don't work. We have this a lot with docpad, where a dependency we've depended on goes haywire, or a new node version breaks something.

It is a matter of parenthood, sometimes things go as planned, sometimes they don't, but always things come out better with a little bit of love, effort, and patience.

As this is a problem with npm, I can try and debug it for you, but it would be like getting a plumber to act as a electrician, you're best off finding out what the issue is on the npm issue tracker, and get it fixed, and you'll be good.

One thing worth mentioning that could help, is that since node v0.8, npm comes bundled with node, so it may be worthwhile just installing the latest node version (v0.10.1) and you'll also get the latest npm version at the same time. Now I would recommended using the bevry installation instructions for installing node - http://bevry.me/node/install - as at least with them, we've tested them on different environments and can guarantee they work - too often than not, we've found that other instructions end up with misconfigured environments, and things go haywire.

Let me know how it goes, I wish I could help further, but my hands are tied as I have client work to attend to, and this issue is outside of docpad's scope for now.

balupton commented 11 years ago

What is the bug exactly? Is it reported? Are these bugs routinely fixed?

NPM is getting confused about the engines that are required, coffee-script satisfies the engines you have (node v0.8)

Therefore it seems it is probably just an issue of your npm version being out of date, so try updating

The update failed as your environment does not appear to be configured correctly (permission wise) - this occurs a lot, which is why we have bevry's node installation instructions

Solutions available to you:

Uninstall your copy of node and install node with the bevry instructions

Install the latest version of node without the bevry instructions and risk the same thing

Post the issue on the npm issue tracker and wait for advice - which would probably be "upgrade npm"

Try this permission workaround - https://github.com/bevry/docpad/issues/469 - and try upgrading npm again

balupton commented 11 years ago

Just finished chatting with @quesada, reinstalling node with the latest bevry instructions fixed the issue http://bevry.me/node/install :)

jdurand commented 11 years ago

I had the same issue. Upgrading node fixed it for me. Thanks!

docpad / docpad

NPM: docpad 6.26 seems to fail to install, maybe because of coffee 1.6? #470

- Jose

- Jose