[SOLVED] Atom 1.3.0 SlackBuild error: Failed at the runas@3.1.1 install script 'node-gyp rebuild'

denydias · 04-07-2016, 03:57 AM

Hello all,

I'm trying to upgrade Atom (the GitHub text editor) to 1.3.0. But it is failing miserably with the following error:

Code:

npm ERR! runas@3.1.1 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the runas@3.1.1 install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the runas package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls runas
npm ERR! There is likely additional logging output above.

My environment is:

Code:

node: v4.4.2
npm: 2.15.0
python-2.7.11-x86_64-2
Slackware 14.2 -current

The problem itself seems quite different from this. I think I've met all the requirements listed here.

Anybody out there faced this issue? Are there any tips to fix this?

Thanks in advance for any advice.

dhabyx · 04-07-2016, 04:12 PM

Hi, You can use my updated slackbuild

https://github.com/dhabyx/slackbuilds/tree/master/atom

denydias · 04-07-2016, 04:41 PM

Hi @dhabyx!

The slackbuild from your repo fails with another error. We're in touch by email. When we get a solution, I come back here to tell the others.

Thank you for your reply.

denydias · 04-07-2016, 06:14 PM

@dhabyx has fixed the issue. A new slackbuild for atom 1.6.2 is avaiable here.

Thank you, @dhabyx!

willysr · 04-07-2016, 09:26 PM

Pushed to my branch as well

thanks

denydias · 04-07-2016, 11:56 PM

Thanks @willysr!

A last minute note: chances are you have installed some packages in your atom if you use it regularly. With the new version of atom kindly provided by @dhabyx, you need to update those. After the new atom finishes to build and get installed, run this in the CLI before firing it up:

Code:

$ atom-apm update

If you just upgrade the SlackBuild provided and forget to update the internal ones, devtools console will show up upon start and you'll not be able to do anything, including to open up the preferences dialog where the package manager sits.