Search Criteria
Package Details: atom 1.61.0beta0-3
Package Actions
Git Clone URL: | https://aur.archlinux.org/atom.git (read-only, click to copy) |
---|---|
Package Base: | atom |
Description: | A hackable text editor for the 21st Century |
Upstream URL: | https://github.com/atom/atom |
Licenses: | MIT |
Replaces: | atom-editor |
Submitter: | alerque |
Maintainer: | alerque |
Last Packager: | alerque |
Votes: | 4 |
Popularity: | 1.62 |
First Submitted: | 2022-06-09 08:13 (UTC) |
Last Updated: | 2022-06-10 08:57 (UTC) |
Dependencies (11)
- apm
- electron11 (electron11-bin)
- libxkbfile
- ripgrep (ripgrep-git)
- git (git-git, git-vfs, git-run-command-patch-git) (make)
- node-gyp (make)
- nodejs-lts-gallium (make)
- npm (nodejs6-bin, nodejs-nightly) (make)
- ctags (vim-jp-ctags, guile-emacs-git, ctags_as3_haxe, ctags-git, uctags-git) (optional) – symbol indexing support
- git (git-git, git-vfs, git-run-command-patch-git) (optional) – Git and GitHub integration
- hunspell (hunspell-git) (optional) – spell check integration
Required by (0)
Sources (12)
- atom.js
- dugite-use-system-git.patch
- fix-atom-sh.patch
- fix-license-path.patch
- fix-restart.patch
- git-utils.patch
- https://github.com/atom/atom/archive/v1.61.0-beta0/atom-1.61.0-beta0.tar.gz
- no-unsafe-eval-warning.patch
- node-env-production.patch
- symbols-view-use-system-ctags.patch
- use-system-apm.patch
- use-system-electron.patch
Latest Comments
dnrops commented on 2022-08-12 17:33 (UTC)
DAC324 commented on 2022-07-01 10:26 (UTC)
@AleyWayfer Thank you very much for pointing this out. Here is
fix-crash-reporter.patch
:AlexWayfer commented on 2022-06-29 11:58 (UTC)
@DAC324 there is lack of
fix-crash-reporter.patch
file for yourPKGBUILD
.DAC324 commented on 2022-06-27 11:02 (UTC)
After having selected
Packages->Command Palette->Toggle->(search for install and select) Application: Install Update
,atom
simply closes. This is actually not a crash butatom
silently quitting, because of the following code:That line
actually seems to do nothing but simply quit the editor. Why?
calls
where
autoupdater
is callingelectron
itself:Indeed, that's not very elegant to simply quit because auto updates do not seem to be supported on Linux
but that's the way it's actually implemented :( Here's a patch that avoids this somewhat ridiculous behavior:
DAC324 commented on 2022-06-24 13:46 (UTC) (edited on 2022-06-27 09:02 (UTC) by DAC324)
Update with regards to that dreaded
undefined symbol: git_net_url_is_default_port
error:Before building
atom
, you will have to remove the compile caches as they contain information that will conflict with your build. Additionally, I got an advice how to get rid of thefix-symbols.patch
. I automated all this in a new version ofPKGBUILD
:This should leave you with an installable
atom
package. Important: if there are still errors, also when startingatom
, delete all compile caches in~/.atom
.DAC324 commented on 2022-06-22 12:08 (UTC)
@kanmeiban I must admit that I also do not understand why that sometimes works and sometimes fails. If you experience that error while issuing
script/bootstrap
in the terminal, try to executescript/clean
before attemptingscript/bootstrap
again.kanmeiban commented on 2022-06-22 07:31 (UTC)
@DAC324 I get the
process.dlopen
duringscript/bootstrap
execution:Anyway, I managed to build the
1.61.0-beta0
using yourfix-symbols.patch
so I think the maintainer @alerque should add it.DAC324 commented on 2022-06-21 17:25 (UTC) (edited on 2022-06-22 13:05 (UTC) by DAC324)
@kanmeiban Please read my previous comment. Unfortunately, it is quite normal that
makepkg
aborts with that error on first run.What to do in that case?
At least that worked for me, and I got a complete package to be installed, for example, with
sudo pacman -U atom-1.63.0.dev.r359.g4b76ccda8-1-x86_64.pkg.tar.zst
kanmeiban commented on 2022-06-21 16:39 (UTC)
@DAC324 I get the
process.dlopen
error when runningscript/bootstrap
.DAC324 commented on 2022-06-21 15:24 (UTC) (edited on 2022-06-22 13:07 (UTC) by DAC324)
In case
makepkg
aborts using myPKGBUILD
, with the following errorgo to your
src/atom
directory and executescript/clean
followed byscript/bootstrap
directly from the terminal. After that has completed, cd back to your package directory and try building the package again.This time, the build process should complete. I must admit that I have no clue what makes the difference between calling
script/bootstrap
fromPKGBUILD
and directly from the terminal.P.S.: Yes, I know that there was
git-utils.patch
designated to fix that issue but this patch does not work anymore (and it also does not appear to be needed asscript/bootstrap
runs without it from the terminal).DAC324 commented on 2022-06-21 12:38 (UTC) (edited on 2022-06-24 13:57 (UTC) by DAC324)
With the transition to atom-community and
atom
version 1.63, things have become a bit easier now. What you need to buildatom-1.63.0-dev
right now isfix-atom-sh.patch
as well asuse-system-apm.patch
from here plus the following patchfix-symbols.patch
along with this
PKGBUILD
:DAC324 commented on 2022-06-17 15:40 (UTC)
The latest upstream version of
atom
is 1.63.0-dev. You can find it at https://github.com/atom-community/atom.gitUnfortunately, there is no tarball available yet, and also the remainder of
PKGBUILD
seems to need some overhaul. In particular, it does not appear to be possible anymore to use system apm and system electron.If you encounter the following error building this package 1.61.0-beta
just apply the following patch to the sources:
maxpayne3 commented on 2022-06-15 22:19 (UTC) (edited on 2022-06-15 22:21 (UTC) by maxpayne3)
Unless a serious fork will show up, this package along with apm it's not really needed. Just keep the previous ones (if you already had them installed) or download them from the archive (if you want a new installation). If yay is complaining about the upgrade, add them to the ignore list.
ConWrite commented on 2022-06-15 18:17 (UTC)
Dead or not, it'd still be nice for the last update to function properly.
gardotd426 commented on 2022-06-15 05:11 (UTC)
This is clearly a situation where the effort needed to keep this AUR package going is pretty much pointless and is better spent elsewhere. Atom is dead. I'm sure a ton of people hate that, and I'm guessing there will be more than one community fork that attempts to continue in its place, but they will likely all just disappear after a short period. My suggestion is to do what you're supposed to do when an AUR package's upstream decides to stop existing - delete the AUR package. Either that, or issue an update that literally says nothing other than "Atom has officially been declared dead, and is being sunset. This AUR package will no longer receive updates. Use at your own risk." Though I think that's the obviously stupid choice, I mean the project is dead, so kill the AUR package that installs the dead project.
maxpayne3 commented on 2022-06-14 16:39 (UTC)
Fortunately I blocklisted
atom
andapm
inpacman.conf
DAC324 commented on 2022-06-13 13:12 (UTC) (edited on 2022-06-13 14:08 (UTC) by DAC324)
The cause of the error I described is with the way
atom
is built in this package.If it is compiled using the commands decribed at https://flight-manual.atom.io/hacking-atom/sections/hacking-on-atom-core/#platform-linux
the source compiles successfully.
Of course, you will need to edit
src/atom-1.63.0-dev/script/lib/dump-symbols.js
:Interesting, though, that it does not seem to matter what
binaryPath.match(/fswin.node/)
returns. It has to be removed from that statement entirely.Looks like the build directives in
PKGBUILD
need some overhaul.
DAC324 commented on 2022-06-11 10:45 (UTC)
Here's a possible solution: https://github.com/atom/atom/issues/25518#issuecomment-1152894318
Replace the Git URL in PKGBUILD by
"https://github.com/atom-community/atom/$pkgname"
However, the guy also writes "atom is now abandoned and the project is concluded."
awilli commented on 2022-06-11 09:56 (UTC)
@DAC324, same Error for me
DAC324 commented on 2022-06-11 09:42 (UTC) (edited on 2022-06-11 10:04 (UTC) by DAC324)
This package does not install:
The error is at line 33 in
src/atom-1.61.0-beta0/script/lib/dump-symbols.js
DrosteEffect commented on 2022-06-10 15:09 (UTC)
@doskanoness Same error for me.
doskanoness commented on 2022-06-10 12:17 (UTC)
I get this error:
awilli commented on 2022-06-10 11:55 (UTC)
I get this error:
alerque commented on 2022-06-10 09:06 (UTC)
Sorry folks, when I migrated this from [community] I apparently migrated the latest trunk build which had some unfinished attempts to modernize the dependencies. I've reverted it to the latest working build that was in the repos so it should build now. Note that you really should compile this in a chroot otherwise you're bound to have dependency mismatches, both with electron and node stuff.
XxTriviumxX commented on 2022-06-10 00:39 (UTC)
i get this error with the when upgrading to 1.61.0beta0-4:
StephanX commented on 2022-06-09 22:02 (UTC)
I'm pretty sad about atom sunsetting; I hope the community maintains it going forward. In the mean time, I'm stuck here:
npm ERR! keyboard-layout@2.0.17 install: node-gyp rebuild
alerque commented on 2022-06-09 08:16 (UTC)
GitHub announced they are sunsetting Atom. Even before that announcement it was trouble in the [community] repo because it depends on an outdated Electron and we were considering dropping it. The sunset announcement that it will not be updated is the last straw. Please welcome Atom to the AUR.