Repository navigation
libcrypto.so.1.0.0 error #13185
Description
Activity
Have you searched the arch forums? For example, have you seen this thread about the same issue?
Reacted by Meysam P. GanjiThat's topic doesn't suggest any instruction for solving the problem. It just says don't do partial update (and generally I always avoid that). For temporary solution, I installed
openssl-1.0to be able to runnode.Reacted by yang chanfa@meysampg This is a downstream (i.e. Arch Linux) issue. The Node.js package is Arch is packaged by Arch Linux maintainers, so the issue should be reported there.
OpenSSL packages in Arch:
testing/openssl-1.0 1.0.2.k-4 core/openssl 1.1.0.e-1 extra/openssl-1.0 1.0.2.k-3Note that there are two separate OpenSSL packages:
opensslandopenssl-1.0.
In Arch,nodejsrequiresopenssl-1.0package which you should have installed for it to run.Node.js packages in Arch:
community/nodejs 7.10.0-1It properly lists
openssl-1.0as a dependency, so unless you updated packages separately (which is kinda not supported in Arch), you should have everything working fine.Another possible reason is that you might have
[testing]repo enabled — Arch Linux maintainers put a new version ofopenssl-1.0there (1.0.2.k-4), but did not rebuildnodejson top of it, socommunity/nodejs 7.10.0-1is still looking forextra/openssl-1.0 1.0.2.k-3. To work-around that, either use the official Node.js binaries or disable the[testing]repo in Arch Linux.Reacted by Chris LaverdiereWhy not use 1.1.0 in nodejs?
@qwIvan see #11828 (comment) and #13575
After a full upgrade of system, every time I tried to run node or a node-based module, I got this error:
This error is related to
opensslwhich the last version of it is1.1.0.e-1but node use version1.0. I tried to use symlinks and solution around it, but they didn't solve the problem.Is there any solution or any coming update to solve this?