It's flagged as out of date anyway lmao, bump it.
Search Criteria
Package Details: atom-editor-git 1.35.0.r1175.g48ca032eb-1
| Git Clone URL: | https://aur.archlinux.org/atom-editor-git.git (read-only, click to copy) |
|---|---|
| Package Base: | atom-editor-git |
| Description: | Hackable text editor for the 21st Century - git channel |
| Upstream URL: | https://atom.io/ |
| Keywords: | text-editor |
| Licenses: | |
| Replaces: | |
| Submitter: | jreese |
| Maintainer: | LevitatingRein (TrialnError) |
| Last Packager: | TrialnError |
| Votes: | 50 |
| Popularity: | 0.046206 |
| First Submitted: | 2014-05-06 18:30 |
| Last Updated: | 2020-01-18 22:02 |
Dependencies (8)
- apm (atom-editor-bin)
- electron4
- libxkbfile
- ripgrep (ripgrep-simd, ripgrep-git)
- git (git-git) (make)
- npm (npm53, npm4, nodejs6-bin) (make)
- ctags (ctags_as3_haxe, vim-jp-ctags, guile-emacs-git, universal-ctags-git) (optional) – symbol indexing support
- git (git-git) (optional) – Git and GitHub integration
Required by (0)
Sources (12)
himanshuxd commented on 2020-01-02 07:28
WSDMatty commented on 2019-10-14 12:00
Looks like upstream changes cause most of the patches to fail.
otaj commented on 2019-03-15 18:03
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:/github.com/kevinsawicki/jasmine-node.git#81af4f953a2b7dfb5bde8331c05362a4b464c5ef" 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().
Aborting...
mrturcot commented on 2019-02-27 06:56
# 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
==> ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace.
==> ERROR: pkgver() generated an invalid version: 1.31.0.dev
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
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
That'd be great to backport the changes from your other package atom-editor-beta ;)
fusion809 commented on 2017-10-16 06:22
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
I just tried to install the package, but I got an error during the packaging process:
==> Making package: atom-editor-git 1.14.0.dev.i1.18.3.l0.5.1.m0.92.2.p1.0.0.u0.39.0.v0.3.2.c30697-1 (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
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/electron-1.3.0-chromedriver-v2.21-linux-x64.zip" 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...
Pinned Comments
fusion809 commented on 2018-03-22 05:00
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.