You are not logged in.
Pages: 1
So I went and updated my Arch installation and now I can't use vagrant anymore, it just spits out:
/opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': libssl.so.1.0.0: cannot open shared object file: No such file or directory - /opt/vagrant/embedded/lib/ruby/2.2.0/x86_64-linux/openssl.so (LoadError)
from /opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /opt/vagrant/embedded/lib/ruby/2.2.0/openssl.rb:17:in `<top (required)>'
from /opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.5/lib/vagrant.rb:57:in `<top (required)>'
from /opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in `require'
from /opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in `rescue in require'
from /opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:39:in `require'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.5/bin/vagrant:62:in `<main>'
I tried removing vagrant with command "pacman -Rsn vagrant" and reinstalling but this didn't help. And yes, I even tried rebooting ![]()
Directory: /opt/vagrant/embedded/lib contains libssl.so.1.0.0 file, but for some reason the binary can't find it.. Any ideas?
"pacman -Qs vagrant" shows the following:
local/vagrant 1.9.5-1
Build and distribute virtualized development environments
local/vagrant-substrate 605.0566498-2
Substrate layer for Vagrant
Last edited by McFish (2017-06-12 17:48:36)
Offline
Hi, I'm not using vagrant, but have you read and tried the steps suggested in the lower part of https://wiki.archlinux.org/index.php/Va … nt-libvirt?
Notably everything starting with "As of June 2017 (Vagrant version 1.9.5-1), a normal installation of this plugin fails,..."
--edit: Or as seth suggests below. Although, I don't think it is a packaging bug, given that vagrant is one of those badly behaved software that bundles all its libraries with itself. Ironically, the way they do it (pretty poorly apparently) causes "library incompatibility"-like issues on their end (see also https://github.com/vagrant-libvirt/vagr … ssues/541).
Last edited by ayekat (2017-06-12 15:03:16)
Offline
pacman -Qi openssl-1.0Apparently it's falsely not a runtime dep of vagrant?
Offline
I ended installing openssl-1.0 package and downgrading vagrant to:
local/vagrant 1.9.2-1
Build and distribute virtualized development environments
local/vagrant-substrate 582.d66af96-1
Substrate layer for Vagrant
Not the most optimal solution, but works for now (tm) ![]()
Offline
Pages: 1