1404 script/build problems with grunt-coffeelint and node-gyp will not build

[marcandrebenoit]

~/bin/atom$ lsb_release -d
Description: Ubuntu 14.04 LTS
~/bin/atom$ uname -i
x86_64
~/bin/atom$ nodejs -v
v0.10.25
~/bin/atom$ npm -v
1.4.10
~/bin/atom$ node-gyp -v
v0.10.10
~/bin/atom$ sudo apt-get install libgnome-keyring-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libgnome-keyring-dev is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
~/bin/atom$ sudo npm config set python /usr/bin/python2 -g

/bin/atom$ script/build
npm ERR! error rolling back Error: EACCES, unlink '/bin/atom/build/node_modules/grunt-coffeelint/node_modules/coffeelint/node_modules/.bin/browserify'
npm ERR! error rolling back grunt-coffeelint@0.0.7 { [Error: EACCES, unlink '/bin/atom/build/node_modules/grunt-coffeelint/node_modules/coffeelint/node_modules/.bin/browserify']
npm ERR! error rolling back errno: 3,
npm ERR! error rolling back code: 'EACCES',
npm ERR! error rolling back path: '/bin/atom/build/node_modules/grunt-coffeelint/node_modules/coffeelint/node_modules/.bin/browserify' }
npm ERR! Error: EACCES, unlink '/bin/atom/build/node_modules/grunt-coffeelint/node_modules/coffeelint/node_modules/.bin/browserify'
npm ERR! { [Error: EACCES, unlink '/bin/atom/build/node_modules/grunt-coffeelint/node_modules/coffeelint/node_modules/.bin/browserify']
npm ERR! errno: 3,
npm ERR! code: 'EACCES',
npm ERR! path: '~/bin/atom/build/node_modules/grunt-coffeelint/node_modules/coffeelint/node_modules/.bin/browserify' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! System Linux 3.13.0-24-generic
npm ERR! command "node" "/usr/local/bin/npm" "--userconfig=~/bin/atom/.npmrc" "install" "--quiet"
npm ERR! cwd ~/bin/atom/build
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.4.10
npm ERR! path /bin/atom/build/node_modules/grunt-coffeelint/node_modules/coffeelint/node_modules/.bin/browserify
npm ERR! code EACCES
npm ERR! errno 3
npm ERR! stack Error: EACCES, unlink '/bin/atom/build/node_modules/grunt-coffeelint/node_modules/coffeelint/node_modules/.bin/browserify'
Usage: gyp_main.py [options ...] [build_file ...]

gyp_main.py: error: no such option: --no-parallel
gyp ERR! configure error
gyp ERR! stack Error: gyp failed with exit code: 2
gyp ERR! stack at ChildProcess.onCpExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:340:16)
gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:797:12)
gyp ERR! System Linux 3.13.0-24-generic
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd ~/bin/atom/build/node_modules/runas
gyp ERR! node -v v0.10.25
gyp ERR! node-gyp -v v0.13.0
gyp ERR! not ok
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! ~/bin/atom/build/npm-debug.log
npm ERR! not ok code 0

[GeoffreyFrogeye]

That's a common issue, remove nodejs and gyp, install nodejs via the official PPA or compile it yourself and re-build atom again.
I should make a pull request to add troubleshooting informations.

[kevinsawicki]

Closing this out thanks to @GeoffreyFrogeye's recommendation

[marcandrebenoit]

i did as per your recommendations and it still isnt working..

[GeoffreyFrogeye]

Try removing current build data.

[Seth-Johnson]

@GeoffreyFrogeye Which official PPA are you referring to? I am getting similar errors and would like to try your suggestion before opening a new issue. Are you talking about this one?

[GeoffreyFrogeye]

@Seth-Johnson Yes, I was. Maybe it's not official, but it's the only one I could found. I need to do some investigation.

[Seth-Johnson]

Well I must admit using that PPA solved my issues.

[marcandrebenoit]

just so where all on the same page.. put up all the steps to install proper.. including the apt-get steps to add the ppa etc etc.. this way we can replicate (and debug) the exact same thing..

[Seth-Johnson]

Okay sure. I did:

sudo apt-add-repository ppa:chris-lea/node.js  
sudo apt-get update  
sudo apt-get install nodejs  
git clone https://github.com/atom/atom
cd atom # There was a version number appended to atom as well, mine was 0.97.0 I think
sudo npm config set python /usr/bin/python2 -g
sudo script/build
sudo script/grunt install  
sudo script/grunt mkdeb
sudo dpkg -i /tmp/atom-build/atom-0.97.0-amd64.deb  

Bingo!

[mortalglitch]

Before I used Seth-Johnson's method on my Linux Mint install I had used the invalid nodejs install and got a similar error to the OP. After this I removed the invalid nodejs and gyp then tried Seth-Johnson's method and I kept getting odd errors regarding unable to parse json package(Sorry I did not copy the error down for exact reference). I then had to

cd ~ 

to the home directory then run

rm .atom -r

to remove any files in the hidden .atom and .npm directory inside of it. After this was complete there was still one .lock file inside the ~.atom/.npm/ I had to remove manually.
After this point I could follow Seth-Johnson's post properly and compiled with no errors.

[thecardcheat]

sudo npm config set python /usr/bin/python2 -g worked for me after script/build errored the first time, however, I had already run sudo npm config set python /usr/bin/python2 -g prior to script/build the first time, so perhaps it was a fluke.

[lock]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!