FS#54903 - [apm] Module version mismatch

Attached to Project: Community Packages
Opened by Carlos Eduardo (cemsbr) - Saturday, 22 July 2017, 02:46 GMT
Last edited by Balló György (City-busz) - Monday, 16 October 2017, 13:15 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Bruno Pagani (ArchangeGabriel)
Nicola Squartini (tensor5)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Can't use apm.

$ apm --help # same error with apm update, apm --version, etc.
module.js:597
return process.dlopen(module, path._makeLong(filename));
^

Error: Module version mismatch. Expected 48, got 57.
at Error (native)
at Object.Module._extensions..node (module.js:597:18)
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)
at require (internal/module.js:20:19)
at Object.<anonymous> (/usr/lib/node_modules/atom-package-manager/node_modules/git-utils/lib/git.js:8:16)
at Object.<anonymous> (/usr/lib/node_modules/atom-package-manager/node_modules/git-utils/lib/git.js:371:4)
at Module._compile (module.js:570:32)


Additional info:
* version 1.18.2-2
This task depends upon

Closed by  Balló György (City-busz)
Monday, 16 October 2017, 13:15 GMT
Reason for closing:  Fixed
Additional comments about closing:  nodejs-lts-argon 4.8.4-2, nodejs-lts-boron 6.11.4-1
Comment by Carlos Eduardo (cemsbr) - Sunday, 23 July 2017, 02:12 GMT
Yes, I'm using the apm from the official Archlinux package:

$ pacman -Ql apm | grep $(which apm)
apm /usr/bin/apm
$ /usr/bin/apm --help
# Same error
Comment by Eli Schwartz (eschwartz) - Sunday, 23 July 2017, 02:13 GMT
There was an update to 1.18.3-1, is this still a problem?
Comment by Carlos Eduardo (cemsbr) - Monday, 24 July 2017, 14:01 GMT
Yes, exactly the same error with 1.18.3-1
Comment by Balló György (City-busz) - Monday, 24 July 2017, 14:47 GMT
Which nodejs version can be found on your system?
Comment by Carlos Eduardo (cemsbr) - Monday, 24 July 2017, 15:07 GMT
community/nodejs-lts-boron 6.11.1-1
Comment by Eli Schwartz (eschwartz) - Monday, 24 July 2017, 15:38 GMT
That would explain a lot, actually. The LTS releases of node don't necessarily play nicely with newer versions of things that depend on them, specifically I think because in this case there are compiled node modules involved.

I think, if we are going to have nodejs LTS packages in the repos, they should provide "nodejs=$pkgver" rather than just "nodejs"... packages that specifically depend on (and are built against) the latest stable nodejs version should explicitly depend on that rather than a provides which can be fulfilled by three different packages two of which are incompatible.
Comment by Balló György (City-busz) - Monday, 24 July 2017, 20:40 GMT
I didn't know that we have another nodejs in the repository...

So we have two problems:

1. nodejs-lts-argon and nodejs-lts-boron should provide nodejs=$pkgver, not just simply nodejs.

2. apm should depend on nodejs>=8.
Comment by Nicola Squartini (tensor5) - Saturday, 05 August 2017, 13:23 GMT
apm depends is fixed in 1.18.3-2.
Comment by Carlos Eduardo (cemsbr) - Monday, 07 August 2017, 03:25 GMT
Now it is working, but I had to uninstall other package depending on LTS. But that's another issue...

Loading...