You are not logged in.
I am using OpenVPN 2.3.14. This version links against openssl 1.0.0 (provided by:
openssl-1.0.2.k-1-x86_64.pkg.tar.xz):
libssl.so.1.0.0 => /usr/lib/libssl.so.1.0.0
libcrypto.so.1.0.0 => /usr/lib/libcrypto.so.1.0.0
However, the pacman links against libcrypto.so.1.1 (provided by openssl-1.1.0.e-1-x86_64.pkg.tar.xz).
For the time-being, I
1) downgraded openssl to openssl-1.0.2.k-1-x86_64.pkg.tar.xz
2) the downgrade broke pacman
3) to fix pacman, copied the libssl.so.1.1 and libcrypto.so.1.1 files into /usr/lib (thank God for using SSH mux and other things so that the session was still open)
So, things are working now.
However, I cannot use pacman to upgrade openssl, even if I want to:
error: failed to commit transaction (conflicting files)
openssl: /usr/lib/libcrypto.so.1.1 exists in filesystem
openssl: /usr/lib/libssl.so.1.1 exists in filesystem
Errors occurred, no packages were upgraded.
Questions
1. How to install both "openssl-1.0.2.k-1-x86_64.pkg.tar.xz" and "openssl-1.1.0.e-1-x86_64.pkg.tar.xz" packages. The libraries can peacefully co-exist - but not the packages.
2. Is there no statically linked version of pacman and other core utilities that can prevent these issues?
Note: this is a VPS and SSH is the only means of access - so cannot boot system using livecd and fix it! A static pacman version will allow me to delete the files in the filesystem and install the updated openssl 1.1 package. Then I can copy the older library files (or use LD_LOAD).
Offline
Edit - post revised
OP:
run this command
pacman --sync --force opensslThen update openvpn. If you can't update it, tell us why.
Future readers:
Beware, using the --force flag is not a good solution to other pacman problems.
Last edited by Hydranix (2017-04-25 18:22:52)
Offline
Is there a reason you can't upgrade your system (and thus openvpn)?
Offline
Yes, regarding OpenVPN - v2.4 has some changes that require me to change my configs and go through testing that I cannot commit to right now. It wasn't a drop-in-place upgrade for me - so had to revert.
Will do that sync thing you mentioned.
However, on another arch machine I have:
$ pacman -Q | grep openssl
openssl 1.1.0.e-1
openssl-1.0 1.0.2.k-3
That is, there is openssl-1.0 & openssl 1.1
Wondering why this is not teh case with this machine.
Offline
Because you have not installed both those packages on your machine?
Offline
$ pacman -Q | grep openssl
openssl 1.1.0.e-1
openssl-1.0 1.0.2.k-3
Pay attention to the names. One package is "openssl", and the other is "openssl-1.0". The "openssl-1.0" package is a separate legacy package that was created to provide libraries from the 1.0 branch alongside the current "openssl" package.
My Arch Linux Stuff • Forum Etiquette • Community Ethos - Arch is not for everyone
Offline