Community Packages

Please read this before reporting a bug:
http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#63426 - [apm] undefined symbol: _ZN2v82V813DisposeGlobalEPPNS_8internal6ObjectE

Attached to Project: Community Packages
Opened by Sébastien Luttringer (seblu) - Saturday, 10 August 2019, 18:43 GMT
Last edited by Evangelos Foutras (foutrelis) - Saturday, 24 August 2019, 18:31 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Nicola Squartini (tensor5)
Architecture All
Severity High
Priority High
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Looks like we are broken again. No atom package upgrade or config access. I give a shot to vscode in the meantime.

$ apm
internal/modules/cjs/loader.js:909
return process.dlopen(module, path.toNamespacedPath(filename));
^

Error: /usr/lib/node_modules/atom-package-manager/node_modules/git-utils/build/Release/git.node: undefined symbol: _ZN2v82V813DisposeGlobalEPPNS_8internal6ObjectE
at Object.Module._extensions..node (internal/modules/cjs/loader.js:909:18)
at Module.load (internal/modules/cjs/loader.js:731:32)
at Function.Module._load (internal/modules/cjs/loader.js:644:12)
at Module.require (internal/modules/cjs/loader.js:771:19)
at require (internal/modules/cjs/helpers.js:68:18)
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 (internal/modules/cjs/loader.js:868:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:879:10)
at Module.load (internal/modules/cjs/loader.js:731:32)
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Saturday, 24 August 2019, 18:31 GMT
Reason for closing:  Fixed
Additional comments about closing:  apm 2.4.2-2
Comment by Bryan L. Gay (linuxninja) - Saturday, 10 August 2019, 19:47 GMT
apm is working for me.
check to see whether you have the package nodejs or one of the other nodejs packages such as nodejs-lts-dubnium (which gets installed when you install signal-desktop)
manually install nodejs to remove and replace any other nodejs package and try your apm command again.
I see this problem often.
Comment by Sébastien Luttringer (seblu) - Saturday, 10 August 2019, 21:23 GMT
I have nodejs from cty-testing. That looks like the same issue than  FS#54280 .
Rollback to nodejs from cty is a workaround.

Don't know much about nodejs machinery, is there a way to predict these breakage between nodejs and apm to rebuild them together in cty-staging before moving to cty-testing?
Comment by Bryan L. Gay (linuxninja) - Sunday, 11 August 2019, 02:48 GMT
looks like apm would need to be built against the nodejs in cty-testing and also placed in cty-testing, per the comments I read on https://bugs.archlinux.org/task/54280

apm works properly when installed with nodejs from community.
Comment by Sébastien Luttringer (seblu) - Sunday, 11 August 2019, 09:31 GMT
Bryan, apm should work in cty-testing. I don't get why you request a bug closure without fixing that.

Loading...