http://bugzilla.opensuse.org/show_bug.cgi?id=1133312 http://bugzilla.opensuse.org/show_bug.cgi?id=1133312#c25 Dan Cermak <dcermak@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |WONTFIX --- Comment #25 from Dan Cermak <dcermak@suse.com> --- (In reply to Alexander Ahjolinna from comment #24)
I still have this same original issue on tumbleweed (20191109), but when I tried to install vagrant-scp pkgs I got an different error...sigh:
vagrant plugin install vagrant-vbguest Installing the 'vagrant-vbguest' plugin. This can take a few minutes... Vagrant failed to properly resolve required dependencies. These errors can commonly be caused by misconfigured plugin installations or transient network issues. The reported error is:
conflicting dependencies bundler (= 1.17.2) and bundler (= 2.0.2) Activated bundler-2.0.2 which does not match conflicting dependency (= 1.17.2)
Conflicting dependency chains: bundler (= 2.0.2), 2.0.2 activated
versus: bundler (= 1.17.2)
Gems matching bundler (= 1.17.2): bundler-1.17.2
Please stop installing vagrant plugins via `vagrant plugin install` if you installed vagrant via zypper unless the plugin is not packaged as an rpm. The vagrant rpm from the openSUSE repositories shares the rubygems with the systemwide ruby installation, which causes odd version conflicts when vagrant tries to install plugins (vagrant's dependency resolution is weird). There is an upstream issue for this: https://github.com/hashicorp/vagrant/issues/10826. If you really want to use `vagrant plugin install`, then please obtain vagrant from upstream directly. They provide an isolated installation, where these kind of conflicts shouldn't appear. Unfortunately, there's really nothing that I can do to prevent these kind of issues, beside patching vagrant to remove the `vagrant plugin install` functionality. -- You are receiving this mail because: You are on the CC list for the bug.