1123845 - ./bin/gaia-test -d fails under ubuntu 14.04

Status: RESOLVED DUPLICATE of bug 1087277

(Firefox OS Graveyard :: Gaia::TestAgent, defect)

Description

[Dave Hylands [:dhylands]]

When I tried to run ./bin/gaia-test -d under Ubuntu 14.04, then I get the following error:
> > ws@0.4.20 install /home/work/B2G-flame-kk/gaia/node_modules/test-agent/node_modules/websocket.io/node_modules/ws
> > node install.js
> 
> npm ERR! weird error 1
> npm WARN This failure might be due to the use of legacy binary "node"
> npm WARN For further explanations, please read /usr/share/doc/nodejs/README.Debian
>  
> npm ERR! not ok code 0
> make: *** [node_modules] Error 1
> gaia-test: Couldn't download a suitable executable for B2G Desktop

It seems that under ubuntu, node.js is instead called nodejs and node is "Amateur Packet Radio Node program"

If I remove /usr/sbin/node and make it be a symlink to /usr/bin/nodejs then gaia-test works properly.

So this bug is to have whatever calls node use nodejs when running under ubuntu.

Comment 1

[Julien Wajsberg [:julienw]]

Please install the package nodejs-legacy which does that for you :) I think I've put this in MDN somewhere but maybe not in the right location?

I'm gonna dupe to bug 1087277 whose role is to detect this and output a better error diagnostic to the user.

Please reopen if simply installing nodejs-legacy does not fix this for you.

Comment 2

[Dave Hylands [:dhylands]]

I was following instrucions on this page:

https://developer.mozilla.org/en-US/Firefox_OS/Platform/Automated_testing/Gaia_unit_tests

which points to https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager and has a brief message about nodejs-legacy, but I didn't think it applied to me since I hadn't intentially installed 'Amateur Packet Radio "Node" Program' and normally I would have though that 'legacy' implied compatibility with old programs.

And the note on https://developer.mozilla.org/en-US/Firefox_OS/Platform/Automated_testing/Gaia_unit_tests talks about making sure you have the "very latest", which to me also implies that I wouldn't need some sort of legacy support.

Installing nodejs-legacy did, in fact remove /usr/sbin/node and /usr/bin/node is a symlink to nodejs.

Comment 3

[Julien Wajsberg [:julienw]]

(In reply to Dave Hylands [:dhylands] from comment #2)
> I was following instrucions on this page:
> 
> https://developer.mozilla.org/en-US/Firefox_OS/Platform/Automated_testing/
> Gaia_unit_tests
> 
> which points to
> https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager
> and has a brief message about nodejs-legacy, but I didn't think it applied
> to me since I hadn't intentially installed 'Amateur Packet Radio "Node"

Yes, I've seen the link to that page, and I don't think it's the right way to do on current Debian, given that stable-backports/testing/unstable all have a recent version [1].

[1] https://packages.debian.org/search?keywords=nodejs

> Program' and normally I would have though that 'legacy' implied
> compatibility with old programs.

Yeah, I agree the naming that Debian chose is really bad here. I guess that implied compatibility with old programs in Debian Archive... But for sure this also brings compatibility with all programs outside of Debian. Maybe we should file a bug there to rename that package to something like nodejs-compat or nodejs-node.

> 
> And the note on
> https://developer.mozilla.org/en-US/Firefox_OS/Platform/Automated_testing/
> Gaia_unit_tests talks about making sure you have the "very latest", which to
> me also implies that I wouldn't need some sort of legacy support.
> 
> Installing nodejs-legacy did, in fact remove /usr/sbin/node and
> /usr/bin/node is a symlink to nodejs.

So it works for you now, right ?


NI Chris Mills to do documentation adjustment.

Comment 4

[Chris Mills [:cmills]]

I've added a note to hopefully cover this, in https://developer.mozilla.org/en-US/Firefox_OS/Platform/Automated_testing/Gaia_unit_tests#Running_unit_tests.

Does this work for you?

Comment 5

[Julien Wajsberg [:julienw]]

Yep this looks good to me.

I keep wondering if MDN has the right tooling for such documentation. Ideally, I'd like to check "I am using Debian/MacOS/Windows" and the article would show the documentation tailored specifically for me.

Comment 6

[Chris Mills [:cmills]]

(In reply to Julien Wajsberg [:julienw] from comment #5)
> Yep this looks good to me.
> 
> I keep wondering if MDN has the right tooling for such documentation.
> Ideally, I'd like to check "I am using Debian/MacOS/Windows" and the article
> would show the documentation tailored specifically for me.

I really appreciate why you'd want this; We were discussing something similar a while ago - so that for example you could select options from a drop down somewhere saying "Show me all platforms", "Show me just Linux", "Show me just Mac", etc. And then this could also be used for regular browser compat info. I think this was being considered as part of our compatibility data project, but I don't think we have anything concrete yet.