Package Details: atom-editor-beta 1.25.0.beta2-1

Git Clone URL: (read-only)
Package Base: atom-editor-beta
Description: Hackable text editor for the 21st Century, built using web technologies on the Electron framework - Beta channel.
Upstream URL:
Keywords: atom beta editor
Licenses: MIT
Conflicts: atom-editor-beta-arch, atom-editor-beta-bin
Provides: atom-editor-beta-bin
Submitter: hydraz
Maintainer: fusion809
Last Packager: fusion809
Votes: 14
Popularity: 1.143085
First Submitted: 2015-12-28 17:00
Last Updated: 2018-02-22 00:38

Latest Comments

Salamandar commented on 2017-10-18 15:13

Yeah \o/
(Still waiting for a better fix for this python2 stuff from them…)

fusion809 commented on 2017-10-18 14:17

It works and I committed it.

fusion809 commented on 2017-10-18 13:40

'twas a remnant of the days when metrics and exception-reporting were things users couldn't disable manually. Going to give this PKGBUILD a go. If it works I'll be committing it thanks.

Salamandar commented on 2017-10-18 13:35

Seemed to be related to a non-clean $srcdir (had the same issue).
1. I did a bit of cleaning on the PKGBUILD, you can find my version here :

2. Why where exception-reporting and metrics disabled ? I had to remove the sed lines in prepare to make the PKGBUILD work.

Now, Atom-beta works.

Salamandar commented on 2017-10-18 11:52

Yes, I was a bit hasty to post my fix :/
But now it's a completely different issue. I'll tell you when everything works.

fusion809 commented on 2017-10-18 10:33

Doesn't work for me gives me this error:

npm ERR! path /data/AUR/atom-editor-beta/src/atom-1.22.0-beta1/apm/node_modules/atom-package-manager/node_modules/npm/node_modules/ansicolors
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall rename
npm ERR! enoent ENOENT: no such file or directory, rename '/data/AUR/atom-editor-beta/src/atom-1.22.0-beta1/apm/node_modules/atom-package-manager/node_modules/npm/node_modules/ansicolors' -> '/data/AUR/atom-editor-beta/src/atom-1.22.0-beta1/apm/node_modules/atom-package-manager/node_modules/npm/node_modules/.ansicolors.DELETE'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR! /home/fusion809/.npm/_logs/2017-10-18T10_32_03_272Z-debug.log
throw err;

Error: Command failed: /data/AUR/atom-editor-beta/src/atom-1.22.0-beta1/script/node_modules/.bin/npm --global-style --loglevel=error install
npm ERR! path /data/AUR/atom-editor-beta/src/atom-1.22.0-beta1/apm/node_modules/atom-package-manager/node_modules/npm/node_modules/ansicolors
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall rename
npm ERR! enoent ENOENT: no such file or directory, rename '/data/AUR/atom-editor-beta/src/atom-1.22.0-beta1/apm/node_modules/atom-package-manager/node_modules/npm/node_modules/ansicolors' -> '/data/AUR/atom-editor-beta/src/atom-1.22.0-beta1/apm/node_modules/atom-package-manager/node_modules/npm/node_modules/.ansicolors.DELETE'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR! /home/fusion809/.npm/_logs/2017-10-18T10_32_03_272Z-debug.log

at checkExecSyncError (child_process.js:592:13)
at Object.execFileSync (child_process.js:612:13)
at module.exports (/data/AUR/atom-editor-beta/src/atom-1.22.0-beta1/script/lib/install-apm.js:9:16)
at Object.<anonymous> (/data/AUR/atom-editor-beta/src/atom-1.22.0-beta1/script/bootstrap:29:1)
at Module._compile (module.js:624:30)
at Object.Module._extensions..js (module.js:635:10)
at Module.load (module.js:545:32)
at tryModuleLoad (module.js:508:12)
at Function.Module._load (module.js:500:3)
at Module.require (module.js:568:17)

Salamandar commented on 2017-10-18 09:47

Well… I found a *really crappy* workaround :
* create a symlink 'python' -> /usr/bin/python2
* add the directory to $PATH
I agree that's horrible but at least that fixes gyp.
in build() :
ln -s /usr/bin/python2 ./python
export PATH=$(pwd):$PATH

Houkime commented on 2017-10-14 19:09

node-gyp is not compatible with python 3 and cannot be even really routed to python2 on modern arch without tons of headache.
This is because the upstream gyp ("thanks" to google) has never been updated to support python 3 (or otherwise mitigate this problem) for around 10 years.
Only now some google-unrelated folks are trying to do it at last

The question to Atom devs is then "Does it really worth it to build your editor using clearly undermaintained stuff?".

Houkime commented on 2017-10-14 18:27

Well, this is embarassing.
I doubt that the problem is in node.js TBH.

When I try to use edited PKGBUILD with just nodejs I get the apm installation loop for sure.

But this isn't the first error that pops up.
If you try to just download sources and build from them after
export PYTHON=<path to python2>
sudo npm config set python /usr/bin/python2 -g

the first error you receive will be still a gyp err!
like this
gyp no longer blames python in general on your machine, but instead an actual script mysteriously has a wrong version.

gyp ERR! configure error
gyp ERR! stack Error: Python executable "/home/username/Downloads/atom-1.22.0-beta1/atom-1.22.0-beta1/apm/node_modules/atom-package-manager/bin/" is v3.6.2, which is not supported by gyp.
gyp ERR! stack You can pass the --python switch to point to Python >= v2.5.0 & < 3.0.0.
gyp ERR! stack at failPythonVersion (/home/username/Downloads/atom-1.22.0-beta1/atom-1.22.0-beta1/apm/node_modules/atom-package-manager/node_modules/node-gyp/lib/configure.js:454:14)
gyp ERR! stack at /home/username/Downloads/atom-1.22.0-beta1/atom-1.22.0-beta1/apm/node_modules/atom-package-manager/node_modules/node-gyp/lib/configure.js:443:9
gyp ERR! stack at ChildProcess.exithandler (child_process.js:197:7)
gyp ERR! stack at emitTwo (events.js:106:13)
gyp ERR! stack at ChildProcess.emit (events.js:191:7)
gyp ERR! stack at maybeClose (internal/child_process.js:877:16)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
gyp ERR! System Linux 4.13.3-1-ARCH
gyp ERR! command "/home/username/Downloads/atom-1.22.0-beta1/atom-1.22.0-beta1/apm/node_modules/atom-package-manager/bin/node" "/home/username/Downloads/atom-1.22.0-beta1/atom-1.22.0-beta1/apm/node_modules/atom-package-manager/node_modules/.bin/node-gyp" "rebuild"
gyp ERR! cwd /home/username/Downloads/atom-1.22.0-beta1/atom-1.22.0-beta1/apm/node_modules/atom-package-manager/node_modules/oniguruma
gyp ERR! node -v v6.9.5
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok

npm ERR! Linux 4.13.3-1-ARCH
npm ERR! argv "/home/username/Downloads/atom-1.22.0-beta1/atom-1.22.0-beta1/apm/node_modules/atom-package-manager/bin/node" "/home/username/Downloads/atom-1.22.0-beta1/atom-1.22.0-beta1/apm/node_modules/atom-package-manager/node_modules/.bin/npm" "rebuild"
npm ERR! node v6.9.5
npm ERR! npm v3.10.10
npm ERR! oniguruma@6.2.1 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the oniguruma@6.2.1 install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the oniguruma 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 information on how to open an issue for this project with:
npm ERR! npm bugs oniguruma
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls oniguruma
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /home/username/Downloads/atom-1.22.0-beta1/atom-1.22.0-beta1/apm/node_modules/atom-package-manager/npm-debug.log

and only THEN a version mismatch.

My personal question about this is "How on earth does gyp know sth about version of The file itself does not include any version info whatsoever."

fusion809 commented on 2017-09-14 21:09

Oops I accidentally committed my tests of nodejs as the dep of this package (instead of nodejs-lts-boron) so I've reverted that. I tested building this package against nodejs-lts-boron and it failed. Not sure how to fix it though. Any ideas anyone?

All comments