search

tensor5 / arch-atom

Repository of Atom and Electron binary packages for Arch Linux
48 stars 5 forks source link

Error when start the Atom Package Manager #8

Closed wyea closed 8 years ago

wyea commented 8 years ago

Hi Nicola, I'm getting the following error. It's more likely a nodejs problem though... But maybe you know how to fix it? It used to work fine a couple days ago... Thanks

$ apm update --all (node:6266) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version. (node:6266) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version. module.js:568 return process.dlopen(module, path._makeLong(filename)); ^

Error: Module version mismatch. Expected 48, got 47. at Error (native) at Object.Module._extensions..node (module.js:568:18) at Module.load (module.js:456:32) at tryModuleLoad (module.js:415:12) at Function.Module._load (module.js:407:3) at Module.require (module.js:466:17) at require (internal/module.js:20:19) at Object. (/usr/lib/node_modules/atom-package-manager/node_modules/git-utils/lib/git.js:8:16) at Object. (/usr/lib/node_modules/atom-package-manager/node_modules/git-utils/lib/git.js:371:4) at Module._compile (module.js:541:32)

tensor5 commented 8 years ago

Thank you for reporting the issue, I didn't do apm update today so I missed it. It's due to nodejs-6.0.0 and fix is on the way.

wyea commented 8 years ago

Hi Nicola! Thank you so much for the fix! Although now apm works, I'm still getting a warning I didn't have before... We should wait until the atom team updates the dependencies of the apm, I guess... Thanks! :-)

apm update --all
(node:23715) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
(node:23715) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
Package Updates Available (0)
tensor5 commented 8 years ago

I noticed that. Fortunately it does not affect the behavior of 'Packages and 'Updates' inside Atom's 'Settings'. The problem is that upstream they ship an old vesion on Node (v0.10.40) together with apm, while we use Arch Linux's nodejs (I don't like duplication, which seems to be the trend nowadays).

severen commented 8 years ago

@tensor5, the issue with Keytar/Nan is supposedly fixed now: atom/node-keytar#40 and atom/node-keytar#41.

tensor5 commented 8 years ago

Apm is already picking up the latest keytar.

severen commented 8 years ago

Sorry hahaha, I missed the obvious message "apm: don't pin keytar version" right above my comment.