Created attachment 435274 [details] The output of "emerge --info '=app-editors/atom-1.7.3-r1'" When trying to update installed Atom packages (plugins) with the apm utility, I am getting the error below: $ apm update Could not determine current Atom version installed Trying the same action via the Atom menu Edit->Preferences->Updates also does not work. The message "Checking for updates..." is displayed forever.
Same here, using system apm $ apm update Could not determine current Atom version installed custom atom /opt/atom/1.7.4/bin/apm update Package Updates Available (1) └── git-time-machine 1.5.2 -> 1.5.3 Using the system "apm", also broke my Atom, when i go to the packages window, I can't see installed packages, to change settings. Today this happened, when I installed the language-dot (https://atom.io/packages/language-dot) And worked when using custom apm (local compiled source code). But I am having some troubles since electron was splitted from this package. Not with default setting, but with custom packages installed, and are not those packages, because with local compiled Atom, everything works!
> Trying the same action via the Atom menu Edit->Preferences->Updates also does not work. The message "Checking for updates..." is displayed forever. This has been fixed in https://bugs.gentoo.org/show_bug.cgi?id=583040
PR with the fix: https://github.com/gentoo/gentoo/pull/1539
(In reply to Elvis Pranskevichus from comment #2) > > Trying the same action via the Atom menu Edit->Preferences->Updates also does not work. The message "Checking for updates..." is displayed forever. > > This has been fixed in https://bugs.gentoo.org/show_bug.cgi?id=583040 I don't think so. I am using app-editors/atom-1.7.4 with dev-util/electron-0.36.12-r1 and am also experiencing this. # /usr/bin/apm ls <works> # /usr/bin/apm update Could not determine current Atom version installed # /usr/bin/apm config list ; cli configs globalconfig = "$HOME/.atom/.apm/.apmrc" user-agent = "npm/2.13.3 node/v5.10.1 linux x64" userconfig = "$HOME/.atom/.apmrc" ; environment configs nodedir = "/usr/include/electron/node/" ; globalconfig $HOME/.atom/.apm/.apmrc cache = "$HOME/.atom/.apm" ; node bin location = /usr/bin/node ; cwd = $HOME ; HOME = $HOME/.atom/.node-gyp ; 'npm config ls -l' to show all defaults.
(In reply to Dennis Schridde from comment #4) > (In reply to Elvis Pranskevichus from comment #2) > > > Trying the same action via the Atom menu Edit->Preferences->Updates also does not work. The message "Checking for updates..." is displayed forever. > > > > This has been fixed in https://bugs.gentoo.org/show_bug.cgi?id=583040 > > I don't think so. I am using app-editors/atom-1.7.4 with > dev-util/electron-0.36.12-r1 and am also experiencing this. I was referring to the specific issue with apm not working from within Atom. That bit has been fixed in #583040.
commit d33147e3af8e63321066f4cd340da473adfe8b6a (HEAD -> master) Author: Elvis Pranskevichus <elvis@magic.io> AuthorDate: Wed May 25 11:11:17 2016 -0400 Commit: Patrice Clement <monsieurp@gentoo.org> CommitDate: Fri May 27 13:46:58 2016 +0000 app-editors/atom: Fix apm under Node 5+. apm monkey-patches Node's module system to add support for module loading from "asar" archives. Add a case to make this work under Node 5+. Gentoo-Bug: https://bugs.gentoo.org/584000 Package-Manager: portage-2.2.28 Closes: https://github.com/gentoo/gentoo/pull/1539 Signed-off-by: Patrice Clement <monsieurp@gentoo.org> app-editors/atom/atom-1.7.4-r1.ebuild | 392 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ app-editors/atom/atom-1.7.4.ebuild | 391 ----------------------------------------------------------------------------------------------------- app-editors/atom/files/asar-require.patch | 45 ++++++++++++ 3 files changed, 437 insertions(+), 391 deletions(-) create mode 100644 app-editors/atom/atom-1.7.4-r1.ebuild delete mode 100644 app-editors/atom/atom-1.7.4.ebuild create mode 100644 app-editors/atom/files/asar-require.patch
