Package Details: atom-editor-git

Git Clone URL: (read-only, click to copy)
Package Base: atom-editor-git
Description: Hackable text editor for the 21st Century - git channel
Upstream URL:
Keywords: text-editor
Licenses: custom, MIT
Conflicts: atom
Provides: atom
Submitter: jreese
Maintainer: SolarAquarion
Last Packager: SolarAquarion
Votes: 49
Popularity: 0.000000
First Submitted: 2014-05-06 18:30 (UTC)
Last Updated: 2021-03-01 04:50 (UTC)

Pinned Comments

SolarAquarion commented on 2021-03-01 02:56 (UTC)

This package Requires npm below 7, so the npm that is in community

eatmyvenom commented on 2021-01-01 22:42 (UTC) (edited on 2021-01-01 22:43 (UTC) by eatmyvenom)


I recently tried to bring this package up to date, however when doing so there was some build error which I didn't know how to fix, most of this package has been updated but its currently unusable and I am unable to fix it. If anyone knows how to do that please take adopt this package and fix it.

Latest Comments

trougnouf commented on 2022-01-07 12:53 (UTC) (edited on 2022-01-07 12:56 (UTC) by trougnouf)

Atom now depends on electron9 not 6 ( )

SolarAquarion commented on 2021-03-01 02:56 (UTC)

This package Requires npm below 7, so the npm that is in community

SolarAquarion commented on 2021-02-26 18:17 (UTC)

@LevitatingRein one of the things i noticed, is that the only thing that is supported is using whatever atom provides

LevitatingRein commented on 2021-02-26 18:03 (UTC)

@SolarAquarion, I noticed you adopted this package. Good luck to you.

eatmyvenom commented on 2021-01-01 22:42 (UTC) (edited on 2021-01-01 22:43 (UTC) by eatmyvenom)


I recently tried to bring this package up to date, however when doing so there was some build error which I didn't know how to fix, most of this package has been updated but its currently unusable and I am unable to fix it. If anyone knows how to do that please take adopt this package and fix it.

LevitatingRein commented on 2020-07-20 11:52 (UTC)

Actually, @TrialnError was assigned as maintainer automatically after I disowned the package. Either he already was a co-maintainer, or I made him co-maintainer because he was the last packager.

Also, @prometheus please keep the comments for serious discussion.

prometheus commented on 2020-07-19 20:47 (UTC)


By trail and error.

TrialnError commented on 2020-06-12 16:30 (UTC)

How did I end up as the maintainer of this?
This PKGBUILD needs someone who is dedicated to keep the patches up to date with the upstream repo and I don't want to do that. I'm happy with the package from the repo.

FabioLolix commented on 2020-06-12 15:14 (UTC)

also need to provide and conflicts atom-editor instead of replace

FabioLolix commented on 2020-06-12 10:20 (UTC)

atom-editor editor from repository is using electron5.

@LevitatingRein you can simply disown the pkgbuild if you don't want to deal with it anymore

LevitatingRein commented on 2020-06-08 08:36 (UTC)

This package is a bit of a shitshow. If aynone wants to fix it be my guest but I am not dealing with it anymore. I'll gladly hand over ownership of the package.

himanshuxd commented on 2020-01-02 07:28 (UTC)

It's flagged as out of date anyway lmao, bump it.

WSDMatty commented on 2019-10-14 12:00 (UTC)

Looks like upstream changes cause most of the patches to fail.

otaj commented on 2019-03-15 18:03 (UTC) (edited on 2019-03-15 18:04 (UTC) by otaj)

Hi, patch use-system-electron.patch fails because atom upstream bumped electron version. However, even when I changed the patch and passed prepare, I was not able to build:

==> Starting build()...
+ node-abi@2.7.1
+ @atom/nsfw@1.0.20
added 877 packages and audited 6153 packages in 5.318s
found 31 vulnerabilities (9 low, 11 moderate, 8 high, 3 critical)
  run `npm audit fix` to fix them, or `npm audit` for details
Installing modules ✗
> atom@1.37.0-dev preinstall /home/otaj/files/aur/atom-editor-git/src/atom-editor-git
> node -e 'process.exit(0)'

npm ERR! code ENOLOCAL
npm ERR! Could not install from "node_modules/jasmine-focused/jasmine-node@git+https:/" as it does not contain a package.json file.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/otaj/.atom/.apm/_logs/2019-03-15T17_58_57_052Z-debug.log
==> ERROR: A failure occurred in build().

mrturcot commented on 2019-02-27 06:56 (UTC) (edited on 2019-02-27 06:56 (UTC) by mrturcot)

# When a piece of software requires this many downstream patches...  
# I think its time to move on to a different editor...  
patch -Np1 -i "${srcdir}"/fix-atom-sh.patch  
patch -Np1 -i "${srcdir}"/use-system-electron.patch  
patch -Np1 -i "${srcdir}"/use-system-apm.patch  
patch -Np1 -i "${srcdir}"/fix-license-path.patch  
patch -Np1 -i "${srcdir}"/fix-restart.patch  
patch -Np1 -i "${srcdir}"/electron-3.patch

That's brutal, thanks for the heads up @mcd1992... Moving along now...

ChrisLahaye commented on 2018-08-12 14:50 (UTC) (edited on 2018-08-12 15:02 (UTC) by ChrisLahaye)

==> ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace.
==> ERROR: pkgver() generated an invalid version:

The cat package.json | grep version is returning multiple lines due to the word version being present in package dependencies URLs (which contain forward slashes). This causes the build to fail.

Maybe use cat package.json | grep version -m1 | sed 's/version//g' | sed 's/[: \/,-\"]//g'

fusion809 commented on 2018-03-22 05:00 (UTC)

Do not flag this as out of date, this is built from git so it automatically updates to the latest version when you build it. You do not need me to bump it to a newer version.

Salamandar commented on 2017-11-01 12:34 (UTC)

That'd be great to backport the changes from your other package atom-editor-beta ;)

fusion809 commented on 2017-10-16 06:22 (UTC)

StripedMonkey -- do not use the out of date flag to report package issues, use the comment! Only use the out of date flag if the package gets outdated which given this is built from git never happens.

Raven commented on 2016-12-31 00:39 (UTC) (edited on 2016-12-31 00:40 (UTC) by Raven)

I just tried to install the package, but I got an error during the packaging process: ==> Making package: atom-editor-git (Sat Dec 31 01:23:06 CET 2016) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Removing existing $pkgdir/ directory... ==> Entering fakeroot environment... ==> Starting package()... cp: cannot stat 'out/atom-1.14.0-dev-26b128d-amd64/*': No such file or directory However the folder exists but just with a slightly different name: out/atom-1.14.0-dev-26b128dd4 (<- the tailing "d4" is missing in the "cp" command) I checked the PKGBUILD file and found that in line 77 there is the expression: _commit=$(git rev-parse --short=7 HEAD) which extracts this commit id from the git repository. - Truncated to 7 characters. So when I changed the expression from "--short=7" to just "--short" (which then extracts the first 9 characters from the git commit id), the installation went fine.

jhofer commented on 2016-12-10 03:11 (UTC)

I am trying to build the package, but it keeps failing soon after all the language files were installed. I stopped the build, cloned everything again, and tried rebuilding the package which still resulted in it failing. This is the terminal output with each failed attempt and reattempt to finish the build: Node: v6.9.2 Npm: v3.10.5 Installing script dependencies Installing apm Installing modules ✓ Wrote Dependencies Fingerprint: /home/jhofer/pkgbuilds/atom-editor-git/src/atom/node_modules/.dependencies-fingerprint 9a4d0581cd49692de4abb7bbe9462a7accf5a0b5 Cleaning /home/jhofer/pkgbuilds/atom-editor-git/src/atom/out Copying assets to /home/jhofer/pkgbuilds/atom-editor-git/src/atom/out/app Transpiling Babel paths in /home/jhofer/pkgbuilds/atom-editor-git/src/atom/out/app Transpiling CoffeeScript paths in /home/jhofer/pkgbuilds/atom-editor-git/src/atom/out/app Transpiling CSON paths in /home/jhofer/pkgbuilds/atom-editor-git/src/atom/out/app Transpiling PEG.js paths in /home/jhofer/pkgbuilds/atom-editor-git/src/atom/out/app Generating module cache for /home/jhofer/pkgbuilds/atom-editor-git/src/atom/out/app Generating pre-built less cache in /home/jhofer/pkgbuilds/atom-editor-git/src/atom/out/app/less-compile-cache Generating metadata for /home/jhofer/pkgbuilds/atom-editor-git/src/atom/out/app/package.json Generating API docs at /home/jhofer/pkgbuilds/atom-editor-git/src/atom/docs/output/atom-api.json Unzipping "/home/jhofer/pkgbuilds/atom-editor-git/src/atom/electron/" to "/home/jhofer/pkgbuilds/atom-editor-git/src/atom/electron/chromedriver" /home/jhofer/pkgbuilds/atom-editor-git/src/atom/script/lib/spawn-sync.js:12 throw result.error ^ Error: spawnSync 7z ENOENT at exports._errnoException (util.js:1022:11) at Object.spawnSync (child_process.js:461:20) at module.exports (/home/jhofer/pkgbuilds/atom-editor-git/src/atom/script/lib/spawn-sync.js:10:41) at unzipPath (/home/jhofer/pkgbuilds/atom-editor-git/src/atom/script/lib/download-chromedriver.js:58:7) at module.exports (/home/jhofer/pkgbuilds/atom-editor-git/src/atom/script/lib/download-chromedriver.js:30:3) at Object.<anonymous> (/home/jhofer/pkgbuilds/atom-editor-git/src/atom/script/build:61:1) at Module._compile (module.js:570:32) at Object.Module._extensions..js (module.js:579:10) at Module.load (module.js:487:32) at tryModuleLoad (module.js:446:12) at Function.Module._load (module.js:438:3) at Module.runMain (module.js:604:10) at run (bootstrap_node.js:394:7) at startup (bootstrap_node.js:149:9) at bootstrap_node.js:509:3 Node: v6.9.2 Npm: v3.10.5 Installing script dependencies Installing apm ^C ==> ERROR: Aborted by user! Exiting... ==> ERROR: A failure occurred in build(). Aborting...

lostkhaos commented on 2016-10-22 13:24 (UTC)

These version numbers are getting a bit intense:

fusion809 commented on 2016-10-15 14:26 (UTC)

Yeah I tried the build yet again and it went without a hitch.

fusion809 commented on 2016-10-15 14:06 (UTC)

What one from GitHub? GitHub doesn't provide a binary for the latest snapshot from the master branch of the Atom repo. For me the package builds fine, although I'm re-building to see if there's anything I can learn that might fix this error of yas.

SolarAquarion commented on 2016-10-15 13:52 (UTC) @fusion809 the one from github works fine but not the one from AUR

SolarAquarion commented on 2016-10-15 13:50 (UTC)

Node: v6.8.1 Npm: v3.10.5 Installing script dependencies Installing apm module.js:327 throw err; ^ Error: Cannot find module '../build/Release/git.node' at Function.Module._resolveFilename (module.js:325:15) at Function.Module._load (module.js:276:25) at Module.require (module.js:353:17) at require (internal/module.js:12:17) at Object.<anonymous> (/home/solaraquarion/.cache/pacaur/atom-editor-git/src/atom/apm/node_modules/atom-package-manager/node_modules/git-utils/lib/git.js:8:16) at Object.<anonymous> (/home/solaraquarion/.cache/pacaur/atom-editor-git/src/atom/apm/node_modules/atom-package-manager/node_modules/git-utils/lib/git.js:371:4) at Module._compile (module.js:409:26) at Object.Module._extensions..js (module.js:416:10) at Module.load (module.js:343:32) at Function.Module._load (module.js:300:12) child_process.js:506 throw err; ^ Error: Command failed: /home/solaraquarion/.cache/pacaur/atom-editor-git/src/atom/apm/node_modules/atom-package-manager/bin/apm --loglevel=error install at checkExecSyncError (child_process.js:483:13) at Object.execFileSync (child_process.js:503:13) at module.exports (/home/solaraquarion/.cache/pacaur/atom-editor-git/src/atom/script/lib/install-atom-dependencies.js:19:16) at Object.<anonymous> (/home/solaraquarion/.cache/pacaur/atom-editor-git/src/atom/script/bootstrap:28:1) at Module._compile (module.js:570:32) at Object.Module._extensions..js (module.js:579:10) at Module.load (module.js:487:32) at tryModuleLoad (module.js:446:12) at Function.Module._load (module.js:438:3) at Module.require (module.js:497:17) Node: v6.8.1 Npm: v3.10.5 Installing script dependencies ^C @fusion809

fusion809 commented on 2016-09-01 05:18 (UTC)

For me whitespace@0.33.0 takes less than a minute to install.

fusion809 commented on 2016-08-31 15:27 (UTC)

I haven't the foggiest why, I don't experience this error.

saikatbsk commented on 2016-08-31 13:20 (UTC) (edited on 2016-08-31 14:45 (UTC) by saikatbsk)

Atom is Installing whitespace@0.33.0 for some three and a half hours. whitespace doesn't seem to be present in aur-atom-editor-git/src/atom/node_modules/ either.

fusion809 commented on 2016-08-31 08:45 (UTC)

Fixed. I found a way to build atom-editor-git despite not receiving any response to that Atom Discuss topic.

fusion809 commented on 2016-08-31 07:31 (UTC)

@saikatbsk Yep, thanks for alerting me to this issue. Unfortunately Atom now uses the `script/build --install` command to install Atom, but it doesn't accept the --install-dir option anymore (which this PKGBUILD uses to install to the `$pkgdir/usr` directory) so I've had to ask a question at Atom Discuss about how to do this (

saikatbsk commented on 2016-08-31 07:02 (UTC)

Error while installing with yaourt. /tmp/yaourt-tmp-saikat/aur-atom-editor-git/./PKGBUILD: line 85: script/grunt: No such file or directory

Awebb commented on 2016-07-13 16:25 (UTC)

You can rejoice and do whatever ritual you usually perform after fixing a bug: It works.

Awebb commented on 2016-07-13 16:21 (UTC)

You fixed it faster than I could build the test. In case you didn't test yourself, I'll report back once this monster is done.

fusion809 commented on 2016-07-13 16:19 (UTC)


Awebb commented on 2016-07-13 16:05 (UTC) (edited on 2016-07-13 16:20 (UTC) by Awebb)

lrwxrwxrwx 1 root root 107 13. Jul 09:20 /usr/bin/apm-git -> /tmp/aur4git/atom-editor-git/pkg/atom-editor-git/usr/share/atom-git/resources/app/apm/node_modules/.bin/apm Something went wrong while building the package. apm-git doesn't work. I suspect line 90 in the PKGBUILD to be the offender, "ln -sf...". I'll see if I can fix it myself. EDIT: I think you could link from "/usr/share/${_pkgname}-${_version}/resources/app/apm/node_modules/.bin/apm" instead of "${pkgdir}/usr/share/${_pkgname}-${_version}/resources/app/apm/node_modules/.bin/apm" 1. It looks like absolute symlinks retain their entire path even through the build process. 2. AFAIK building and packaging happens in a chroot as nobody as the current user, so the process should not be able to damage anything in the real tree. 3. symlinks only need a valid target, not a valid source. You can "ln -s foo bar" any time to create a symlink to foo, even if foo does not exist. I'll try this. EDIT: Building this thing takes time! I built it over night last time. If Atom wasn't such a fine piece of software, I wouldn't touch that node stuff with a pitchfork. /rant

fusion809 commented on 2016-06-30 14:55 (UTC)

@clever Ah for me it works fine. Sure it's not a networking issue on your side? To check you can git clone Atom's repo manually with: git clone

clever commented on 2016-06-30 14:21 (UTC)

Git Clone downloads over 108MB and at the end failed,Tried over & over.

fusion809 commented on 2016-06-05 14:00 (UTC)

@yalker24 My apologies, 'tis fixed now.

yalker24 commented on 2016-06-05 13:52 (UTC) (edited on 2016-06-05 13:53 (UTC) by yalker24)

@fusion809 If i try to run atom-git after installing this package, i get the error that '/usr/share/atom/atom' could not be found. This is due to Line 42 inside the atom-git executable, which resides in /usr/bin. Line 42 contains 'ATOM_PATH="$USR_DIRECTORY/share/atom/atom"', but should be 'ATOM_PATH="$USR_DIRECTORY/share/atom-git/atom"', as the package is installed there. aside from that it works without a problem, thanks for taking over the package.

fusion809 commented on 2016-06-04 03:29 (UTC)

Done. I'm interested in feedback, I think this package, seeing how it's in the AUR, really belongs to the Arch community. So I'm willing to make adjustments to this package to make the community happier.

MarcinWieczorek commented on 2016-06-03 16:31 (UTC)

@fusion809 just adopt it.

fusion809 commented on 2016-06-01 15:03 (UTC)

If someone would add me as a maintainer I would be happy to. I even have a PKGBUILD ready My PKGBUILD will allow atom-editor and atom-editor-git to be installed simultaneously to one another.

Gryffyn commented on 2016-06-01 11:37 (UTC)

you're welcome, fusion809

therojam commented on 2016-06-01 09:09 (UTC)

package could be deleted!

commented on 2016-02-06 08:28 (UTC)

@fusion809 Actually it seems Gryffin as already taken it over

fusion809 commented on 2016-02-02 12:29 (UTC) (edited on 2016-02-02 12:32 (UTC) by fusion809)

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,

commented on 2015-10-02 18:37 (UTC)

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 (UTC)

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(). Aborting... ==> ERROR: Makepkg was unable to build atom-editor-git.

commented on 2015-09-28 10:19 (UTC)

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

onny commented on 2015-09-27 19:33 (UTC)

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)/..) ATOM_PATH="$USR_DIRECTORY/share/atom/atom" ATOM_HOME="${ATOM_HOME:-$HOME/.atom}" + export PYTHON=python2 mkdir -p "$ATOM_HOME"

commented on 2015-09-24 19:15 (UTC)

@rbellamy 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 (UTC)

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:

commented on 2015-09-23 15:21 (UTC)

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

TrialnError commented on 2015-09-23 12:11 (UTC)

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)

commented on 2015-09-17 08:53 (UTC)

From the wiki: epoch Warning: epoch should only be used when absolutely required to do so. Are you sure it doesn’t update? here it works fine Btw, As I no longer use the git version of atom, if somebody wants to step in I’ll be glad to disown the package

stobbsm commented on 2015-09-16 14:44 (UTC)

You should add an epoch to this build, as the current git won't update this package as is.

commented on 2015-09-11 17:21 (UTC)

I also don't understand it... I will look into it when I have more time! Thanks, for your reply! Andrie...

commented on 2015-09-11 13:37 (UTC)

@anrie Here it works fine.. I can’t understand what’s happening. Does somebody have any clue?

commented on 2015-09-11 07:51 (UTC)

user@host$: bash <(curl -si atom-editor-git % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 168 100 168 0 0 169 0 --:--:-- --:--:-- --:--:-- 169 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 1432 0 1432 0 0 1268 0 --:--:-- 0:00:01 --:--:-- 1269 ==> Making package: atom-editor-git v1.0.7.r46.g927ec7a-1 (Fri Sep 11 09:49:26 SAST 2015) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Updating atom git repo... Fetching origin -> Found atom-python.patch ==> Validating source files with md5sums... atom ... Skipped atom-python.patch ... Passed ==> Extracting sources... -> Creating working copy of atom git repo... Reset branch 'makepkg' ==> Starting pkgver()... ==> Updated version: atom-editor-git v1.0.11.r110.gbc68056-1 ==> Starting prepare()... patching file ==> Removing existing $pkgdir/ directory... ==> Starting build()... Node: v0.12.7 npm: v2.14.3 Installing build modules... Installing apm... /bin/sh: /home/apie/atom-editor-git/src/atom/build/node_modules/.bin/npm: No such file or directory ==> ERROR: A failure occurred in build(). Aborting... What is the problem... Any help would be appreciated!

commented on 2015-08-15 09:38 (UTC)

I’m glad =D

uncle commented on 2015-08-15 09:15 (UTC)

Yeah, that fixed the constant update message I was having, it appears to be working correctly now.

commented on 2015-08-15 09:11 (UTC)

@uncle Could you please try it now? I think you are right, the problem should be the change in how the version number is displayed. If it’s this, from now on it should work fine.. we’ll know on next release

commented on 2015-08-15 08:56 (UTC)

@uncle I’ll try it now, I don’t know what’s happening yet

uncle commented on 2015-08-15 00:29 (UTC)

Deleted my comment, and am reposting to better explain. Im not sure exactly what the problem is, but it appears there is an issue with the package's version numbering. Yaourt constantly tells me there is an update, even though I just installed the package, and have updated repeatedly. "==> Software upgrade (new version) : aur/atom-editor-git v1.0.7.r46.g927ec7a-4 -> 0.209.0.r18.g01be252-4" The PKGBUILD lists the pkgver as "0.209.0.r18.g01be252", but if you copy the code responsible for updating pkgver and run it in a local copy of the atom github repo it will return "v1.0.7.r46.g927ec7a" perhaps something recently changed in the atom repo which causes the version number to be displayed differently? I realize that the package is actually up to date on my machine, it is just annoying to always have an out-of-date notification.

commented on 2015-06-13 12:19 (UTC)

The patch was created by the original submitter here: It was 4 months before I’ll ask the submitter about this

commented on 2015-06-13 12:14 (UTC)

@TrialnError I updated the pkgbuild: base-devel was removed, python patch was added. I’ll do some further investigation, but for now let’s just keep it to be safe

TrialnError commented on 2015-06-13 12:04 (UTC)

@andya: But the installed python files still have the /usr/bin/env python as shebang. So if this export is reset problems will occur, which gets circumvented by the export command in the So I think was it intended. If it's really necessary. I dunno at the moment

oozyslug commented on 2015-06-13 12:00 (UTC)

@TrialnError noted . Thank you for that info . I guess I should read the guidelines more carefully :D

commented on 2015-06-13 11:56 (UTC)

I’ll remove base-devel. As for the patch, I think we can remove it: maybe it was created before this commit:

TrialnError commented on 2015-06-13 11:53 (UTC)

@oozyslug: And I hoped the other builds could get rid of it :D And in case of the base-devel: It maybe doesn't hurt. But the Guidelines for AUR and all stuff using makepkg states to not include them.

commented on 2015-06-13 11:51 (UTC)

@TrialnError Both changes were based on upstream docs here: For Arch: sudo pacman -S gconf base-devel git nodejs libgnome-keyring python2 export python=/usr/bin/python2 before building Atom. I built this without the python patch and it works just fine, both the editor and apm. Let me know what you prefer to do about this. Actually base-devel could be safely removed from dependencies, I think.

oozyslug commented on 2015-06-13 11:17 (UTC)

you are right @TrialnError . The patch file is required . I made a mistake and asked the maintainer to rip it off . The maintainer will fix the problem . Sorry . Thank you for pointing it out. As for the case of base-devel group , It doesn't hurt to have it in the dependencies since listing it only notifies pacman. I don't believe that will be a problem. Maintainer will make the decision here though

TrialnError commented on 2015-06-13 10:53 (UTC)

Two notes: First, It's true that base and base-devel are requirements for AUR. But as this is the case those packages won't be included in the depends line. And adding the whole group is somewhat wrong in this case. (pacman, gawk, which aren't really packages this program relies upon for example) Second. More like a question. Did upstream change something which makes the python2 patch obsolete? The other packages still include it

TrialnError commented on 2015-02-19 23:15 (UTC)

The sed command needs to adjusted. Currently the generated Atom.desktop has a wrong entry for Exec And I'm not sure if the any-Architecture is the right thing. Imo it should be ('x86_64' 'i686'). But that is something namcap can tell you

Nefelim4ag commented on 2015-02-08 20:18 (UTC)

@hazard, this is not a package error, just a atom itself, like at now its can't compile with nodejs v0.12

hazard commented on 2015-02-05 07:13 (UTC)

Can't be sure but something doesn't seem right: I did notice during packaging: ==> Creating package "atom-editor-git"... -> Generating .PKGINFO file... -> Generating .MTREE file... -> Compressing package... bsdtar: usr/share/atom/resources/app/node_modules/markdown-preview/spec/fixtures/subdir/áccénté Can't translate pathname 'usr/share/atom/resources/app/node_modules/markdown-preview/spec/fixtures/subdir/áccénté' to UTF-8 bsdtar: usr/share/atom/resources/app/node_modules/markdown-preview/spec/fixtures/subdir/áccénté Can't translate pathname 'usr/share/atom/resources/app/node_modules/markdown-preview/spec/fixtures/subdir/áccénté' to UTF-8 ==> Leaving fakeroot environment. ==> Finished making: atom-editor-git 0.177.0.r63.g83c8d90-1

Nefelim4ag commented on 2015-02-03 04:25 (UTC)

Okay, i will be a maintainer.

jreese commented on 2015-01-16 22:49 (UTC)

If anyone is interested in maintaining the atom-editor and atom-editor-git packages on the AUR, please let me know. I haven't been using Atom for a few months now, so it'd be nice to find someone more involved in the project to keep these builds going.

codebam commented on 2014-12-07 23:07 (UTC)

Make sure to follow instructions here for npm (under requirements) and arch linux before building.

Cacodaemon commented on 2014-09-30 15:06 (UTC)

The editor crashes with an "Bus error" after an update. Installation: Try to start and gdb:

jreese commented on 2014-07-25 02:05 (UTC)

Fixed the patch for forcing python2.

jreese commented on 2014-07-07 20:19 (UTC)

Updated build process to pass --install-dir to the build script, which should fix the issue with needing permissions to write to /usr when building the package.

jreese commented on 2014-06-26 00:31 (UTC)

Fixed Atom.desktop

Pulse commented on 2014-06-25 00:11 (UTC)

Unfortunately, something is a little bit broken with this and your other atom-editor packages. During install I noticed: npm ERR! registry error parsing json - git version npm WARN package.json github-url-from-git@1.1.1 No repository field Also, when the install finishes the application won't launch with the following: Failed to execute command "Chrome-based text editor from Github/share/atom/atom %U". Failed to execute child process "Chrome-based" (No such file or directory) It's possible to launch directly from /usr/share/atom/atom but when doing so some atom packages don't work, for example tree-view. Finally, the application does seem to work correctly when run from the console, which I assume is running the shell script in /bin?

jreese commented on 2014-06-20 14:20 (UTC)

Reenabled i686.

giodamelio commented on 2014-06-20 06:01 (UTC)

Atom supports 32bit now.

antonioromero commented on 2014-05-29 07:31 (UTC)

I recommend

antonioromero commented on 2014-05-29 07:17 (UTC)

It seems that is a problem with gnome-keyring: /bin/sh: pkg-config: no se encontró la orden gyp: Call to 'pkg-config --libs-only-l gnome-keyring-1' returned exit status 127. while trying to load binding.gyp

antonioromero commented on 2014-05-27 15:35 (UTC)

Hi! I get the following errors while installing: npm ERR! System Linux 3.14.4-1-ARCH npm ERR! command "node" "/home/antonio/atom/build/node_modules/.bin/npm" "--userconfig=/home/antonio/atom/.npmrc" "install" "--quiet" npm ERR! cwd /home/antonio/atom/apm npm ERR! node -v v0.10.28 npm ERR! npm -v 1.4.13 npm ERR! path /home/antonio/atom/apm/node_modules/atom-package-manager/node_modules/plist/tests/iTunes-BIG.xml npm ERR! fstream_path /home/antonio/atom/apm/node_modules/atom-package-manager/node_modules/plist/tests/iTunes-BIG.xml npm ERR! fstream_type File npm ERR! fstream_class FileWriter npm ERR! code ENOENT npm ERR! errno 34 npm ERR! fstream_stack /home/antonio/atom/build/node_modules/npm/node_modules/fstream/lib/writer.js:284:26 npm ERR! fstream_stack Object.oncomplete (fs.js:107:15) npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /home/antonio/atom/apm/npm-debug.log npm ERR! not ok code 0 Thanks in advance!

jreese commented on 2014-05-21 00:20 (UTC)

Added dependency on libatomic_ops.

giodamelio commented on 2014-05-14 20:25 (UTC)


FernandoBasso commented on 2014-05-14 20:23 (UTC)

Is this really only x86_64?

joerg-krause commented on 2014-05-14 07:12 (UTC)

Building with aura failed for me: npm WARN package.json github-url-from-git@1.1.1 No repository field. Unable to download getaddrinfo ENOTFOUND ==> ERROR: A failure occurred in build(). Aborting... Installing modules ✓ Installing atom-dark-syntax@0.15.0 ✗ aura >>= Would you like to continue anyway? [Y/n] n aura >>= Building failed.

jreese commented on 2014-05-13 18:54 (UTC)

Fixed python2 support thanks to @hexchain, and modified Atom.desktop to use the /usr/bin/atom wrapper script.

jreese commented on 2014-05-12 21:28 (UTC)

Fixed the packaging script from the previous revision, and added the provides('atom-editor') statement.

jreese commented on 2014-05-12 17:48 (UTC)

Removed as dependency, changed libgcrypt15 dep to libgcrypt, and updated install commands per @willemw's suggestion.

jleclanche commented on 2014-05-12 15:48 (UTC)

The dependency can be dropped now. libgcrypt15 can be replaced by libgcrypt.

willemw commented on 2014-05-12 12:07 (UTC)

Please add: provides=('atom-editor'). (Please use 'install -dm755' and 'install -Dm644' here.)

sathyamvellal commented on 2014-05-08 04:22 (UTC)

I get a build error: ../src/ fatal error: gnome-keyring.h: No such file or directory #include <gnome-keyring.h>

arch_arcade commented on 2014-05-08 00:40 (UTC)

@orschiro: works for me via yaourt

1ace commented on 2014-05-07 22:56 (UTC)

@orschiro: works for me with `pacaur` :)

orschiro commented on 2014-05-07 21:19 (UTC)

Anyone successfully installed this package using an AUR helper such as Aura? For me it stops after running "install" task although there is no error: Installing language-yaml@0.6.0 ✓ Deduping modules ✓ Running "download-atom-shell" task Running "build" task Running "coffee:glob_to_multiple" (coffee) task Running "prebuild-less:src" (prebuild-less) task Running "cson:glob_to_multiple" (cson) task >> 153 files compiled to JSON. Running "peg:glob_to_multiple" (peg) task Running "generate-license:save" (generate-license) task Running "set-version" task Done, without errors. Running "install" task aura >>= Would you like to continue anyway? [Y/n]

jreese commented on 2014-05-07 20:26 (UTC)

Added dependencies from namcap, removed x86 from arch list, and added license to /usr/share/licenses.

giodamelio commented on 2014-05-07 17:09 (UTC)

For the time being atom is 64bit only. See

mus commented on 2014-05-07 17:07 (UTC)

this should conflict with atom-editor. thanks

Rasi commented on 2014-05-07 15:58 (UTC)

please add libnotify to deps

cryptix commented on 2014-05-07 11:50 (UTC)

I got "/usr/share/atom/atom: error while loading shared libraries: cannot open shared object file: No such file or directory" might add extra/gconf to the deps.

devm33 commented on 2014-05-07 08:45 (UTC)

I got the following error when I ran atom on Archlinux x86: $ atom /usr/share/atom/atom: /usr/share/atom/atom: cannot execute binary file This is because /usr/share/atom/atom is a ELF 64-bit binary. $ file /usr/share/atom/atom /usr/share/atom/atom: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=df5bcd9148b1d2bc25cc67897774c561fe1d2170, stripped Does atom support i686 32-bit binary?

dare023 commented on 2014-05-07 08:43 (UTC)

Does not start : /usr/share/atom/atom: /usr/share/atom/atom: cannot execute binary file

jreese commented on 2014-05-07 00:48 (UTC)

Install to /usr, added desktop application entry and pixmap.

jreese commented on 2014-05-06 22:43 (UTC)

Experimenting with that at the moment, wanted to verify that there wasn't anything relying on /usr/local before making the change to the PKGBUILD.

badboy commented on 2014-05-06 22:37 (UTC)

This should be installed into /usr, not /usr/local

jreese commented on 2014-05-06 21:49 (UTC)

Fixed arch.

jreese commented on 2014-05-06 21:31 (UTC)

Fixed dependencies, added INSTALL_PREFIX. atom-editor still bombs out during build, but it seems that atom-editor-git builds correctly now.

underoot commented on 2014-05-06 21:30 (UTC)

Thanks =) Get my vote!

underoot commented on 2014-05-06 21:23 (UTC)

jreese, libgcrypt from AUR - libgcrypt15. Just there is not in official arch package.

1ace commented on 2014-05-06 21:13 (UTC)

Please remove your "fix" for the `` problem, and either use the `` workaround package or actually fix the problem (`sed` one-liner): Also, the generated package is not architecture-independent, so you should list compatible architectures in the `arch` array (i686 & x86_64 as far as I know). Once those two are fixed, you have my vote ;) (You haven't pushed your PKGBUILD to your, so I couldn't simply send you a pull-request :)

tesfabpel commented on 2014-05-06 20:28 (UTC)

I have the same problem as k4nar

underoot commented on 2014-05-06 20:21 (UTC)

There is not libgcrypt15 in the list of dependencies. Why? When I tryed install manually from GitHub, binnary file demanded

k4nar commented on 2014-05-06 20:11 (UTC)

I just tried to install it (as atom-editor was failing), but I'm getting this error (not the same than with atom-editor) : Running "set-version" task Done, without errors. ==> Entering fakeroot environment... ==> Starting package()... Running "install" task Aborted due to warnings.