Package Details: atom-editor-git 1.1.0.beta.0.r178.g575d79a-2

Git Clone URL: (read-only)
Package Base: atom-editor-git
Description: Chrome-based text editor from Github
Upstream URL:
Keywords: text-editor
Licenses: MIT
Conflicts: atom-editor, atom-editor-bin
Provides: atom-editor
Submitter: jreese
Maintainer: Gryffyn
Last Packager: andya
Votes: 40
Popularity: 0.168154
First Submitted: 2014-05-06 18:30
Last Updated: 2015-09-30 10:10

Latest Comments

andya commented on 2016-02-06 08:28

Actually it seems Gryffin as already taken it over

fusion809 commented on 2016-02-02 12:29

I'll take responsibility for it, although I plan on making it build the latest stable release of Atom from git (similarly to how the gvim-git package does). See this question of mine at Unix & Linux SE, for example,

andya commented on 2015-10-02 18:37

I’m orphaning the package; I don’t use it anymore and it requires lots of skill (that I don’t have) to solve some recurrent build errors (@archie, @rbellamy).
Hopefully somebody will take it up?
Please feel free to contact me if you need information on the pkgbuild.

sLite commented on 2015-09-30 08:06

getting the following at the moment:

Running "install" task

Done, without errors.
install: cannot stat ‘resources/atom.png’: No such file or directory
==> ERROR: A failure occurred in package().
==> ERROR: Makepkg was unable to build atom-editor-git.

andya commented on 2015-09-28 10:19

I deleted the patch, that wasn’t needed anymore; your issue should be solved

onny commented on 2015-09-27 19:33

Get following error:

==> Starting prepare()...
patching file
Hunk #1 FAILED at 76.
1 out of 1 hunk FAILED -- saving rejects to file
==> ERROR: A failure occurred in prepare().

% cat
--- 2014-07-24 18:49:00.022810114 -0700
+++ 2014-07-24 18:49:15.993257782 -0700
@@ -76,6 +76,7 @@
USR_DIRECTORY=$(readlink -f $(dirname $SCRIPT)/..)
+ export PYTHON=python2

mkdir -p "$ATOM_HOME"

andya commented on 2015-09-24 19:15

I’m quite sure this is an upstream bug, so we can’t do anything from the pkgbuild side...
It seems there are many people having random problems compiling with node (this is why I decided to just stick with the precompiled package)

rbellamy commented on 2015-09-24 17:43

I'm getting a build error when running makepkg:
67283 warn EPACKAGEJSON atom-build@ No license field.
67284 verbose stack Error: runas@2.0.0 install: `node-gyp rebuild`
67284 verbose stack Exit status 1
67284 verbose stack at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:233:16)
67284 verbose stack at emitTwo (events.js:87:13)
67284 verbose stack at EventEmitter.emit (events.js:172:7)
67284 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:24:14)
67284 verbose stack at emitTwo (events.js:87:13)
67284 verbose stack at ChildProcess.emit (events.js:172:7)
67284 verbose stack at maybeClose (internal/child_process.js:817:16)
67284 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
67285 verbose pkgid runas@2.0.0
67286 verbose cwd /tmp/pkgbuild-1000/atom-editor-git/src/atom/build
67287 error Linux 4.1.6-1-ARCH
67288 error argv "/usr/bin/node" "/usr/bin/npm" "--userconfig=/tmp/pkgbuild-1000/atom-editor-git/src/atom/build/.npmrc" "install" "--loglevel" "error"
67289 error node v4.1.1
67290 error npm v3.3.3
67291 error code ELIFECYCLE
67292 error runas@2.0.0 install: `node-gyp rebuild`
67292 error Exit status 1
67293 error Failed at the runas@2.0.0 install script 'node-gyp rebuild'.
67293 error This is most likely a problem with the runas package,
67293 error not with npm itself.
67293 error Tell the author that this fails on your system:
67293 error node-gyp rebuild
67293 error You can get their info via:
67293 error npm owner ls runas
67293 error There is likely additional logging output above.
67294 verbose exit [ 1, true ]
Found similar issue on Mac OS X, but though the OP got it to build, atom wouldn't launch for him:

Here's a GitHub issue:

Which points to an improper 'runas' requirement:

andya commented on 2015-09-23 15:21

Thank’you very much @TrialnError! I updated the package

TrialnError commented on 2015-09-23 12:11

Sounds like someone is using an AUR helper like yaourt. VCS packages don't work that well with those. And epoch for AUR packages is generally unnecessary.

What you should change is the sed command and add ;s/^v// to filter this v from the version string (to make a proper version)

All comments