search

binarybucks / homA

An extensible framework for the smart home
Eclipse Public License 1.0
137 stars 24 forks source link

Could not install nools #129

Closed llauren closed 9 years ago

llauren commented 10 years ago

Pardon my nubicity, but i have no idea whether this error is due to the homA Rules component or something else.

I tried running the rules component and got informed that i don't have the nools node module installed. So i run npm install and get a bunch of ugly error messaging. The failure begins with

npm http GET https://registry.npmjs.org/keypress
npm http GET https://registry.npmjs.org/keypress/-/keypress-0.1.0.tgz
npm ERR! failed to fetch https://registry.npmjs.org/keypress/-/keypress-0.1.0.tgz
npm ERR! error installing commander@1.1.1
npm ERR! error installing nools@0.2.2

For reasons beyond my understanding, all other npm http GET lines have a simple url whereas the failing keypress url has the unexpected hypen and an actual file name. It might all be my fault or lack of understanding and in no way an issue at all, but if you could just nudge me in the right direction, i'd be more than happy.

binarybucks commented 10 years ago

Hi there,

I just ran npm install in the rules directory and it worked like a charm. Also, npm was able to fetch keypress just fine. Could you try to run it again, maybe it was just a temporal npm glitch. If not, what version of node and npm are you using?

On Sun, Mar 2, 2014 at 8:47 PM, Robin Laurén notifications@github.comwrote:

Pardon my nubicity, but i have no idea whether this error is due to the homA Rules component or something else.

I tried running the rules component and got informed that i don't have the nools node module installed. So i run npm install and get a bunch of ugly error messaging. The failure begins with

npm http GET https://registry.npmjs.org/keypress/-/keypress-0.1.0.tgz npm ERR! failed to fetch https://registry.npmjs.org/keypress/-/keypress-0.1.0.tgz npm ERR! error installing commander@1.1.1 npm ERR! error installing nools@0.2.2

It might all be my fault or lack of understanding and in no way an issue at all, but if you could just nudge me in the right direction, i'd be more than happy.

— Reply to this email directly or view it on GitHubhttps://github.com/binarybucks/homA/issues/129 .

Mit freundlichen Grüßen / With kind regards Alexander Rust

llauren commented 10 years ago

Still getting the errors.

~ $ node --version v0.6.19 ~ $ npm --version 1.1.4

So it's old, even though Aptitude didn't think so :-/

On 3 March 2014 09:19, Alexander Rust notifications@github.com wrote:

Hi there,

I just ran npm install in the rules directory and it worked like a charm. Also, npm was able to fetch keypress just fine. Could you try to run it again, maybe it was just a temporal npm glitch. If not, what version of node and npm are you using?

On Sun, Mar 2, 2014 at 8:47 PM, Robin Laurén notifications@github.comwrote:

Pardon my nubicity, but i have no idea whether this error is due to the homA Rules component or something else.

I tried running the rules component and got informed that i don't have the nools node module installed. So i run npm install and get a bunch of ugly error messaging. The failure begins with

npm http GET https://registry.npmjs.org/keypress/-/keypress-0.1.0.tgz npm ERR! failed to fetch https://registry.npmjs.org/keypress/-/keypress-0.1.0.tgz npm ERR! error installing commander@1.1.1 npm ERR! error installing nools@0.2.2

It might all be my fault or lack of understanding and in no way an issue at all, but if you could just nudge me in the right direction, i'd be more than happy.

Reply to this email directly or view it on GitHub< https://github.com/binarybucks/homA/issues/129> .

Mit freundlichen Grüßen / With kind regards Alexander Rust

Reply to this email directly or view it on GitHubhttps://github.com/binarybucks/homA/issues/129#issuecomment-36486489 .

What is optimism, but (positive) denial of reality?

simonvanderveldt commented 9 years ago

ping @llauren is this still happening for you? It worked for me with no problems whatsoever, maybe it was a temporary glitch in combination with a specific/older node/npm version?

llauren commented 9 years ago

Hi @simonvanderveldt ! Good to see you working on this project!

I haven't tried this for quite some time, so i cannot confirm i still have a problem. I'll close this bug and re-open it if i still get problems :smile:

llauren commented 9 years ago

Cannot replicate.

simonvanderveldt commented 9 years ago

:+1: