![]() > Being able to install plugins using "vagrant plugin install" is a (In reply to Uri Simchoni from comment #4) I will try, locally, upgrading vagrant-libvirt on F26 to 0.0.40 and see if that changes the result. ![]() ![]() => default: Installed the plugin 'vagrant-azure (2.0.0)'! => default: /usr/share/ruby/psych.rb:230: warning: previous definition of FALLBACK was here => default: /usr/share/gems/gems/psych-2.2.2/lib/psych.rb:230: warning: already initialized constant Psych::FALLBACK => default: /usr/share/ruby/psych.rb:228: warning: previous definition of LIBYAML_VERSION was here => default: /usr/share/gems/gems/psych-2.2.2/lib/psych.rb:228: warning: already initialized constant Psych::LIBYAML_VERSION => default: Installing the 'vagrant-azure' plugin. => default: ++ vagrant plugin install vagrant-azure When I use `fedora/26-cloud-base` instead, it runs smoothly: I've used the following Vagrantfile:Ĭonfig.vm.box = ruby vagrant-libvirt rubygem-nokogiri'Ĭonfig.vm.provision "shell", inline: default: vagrant-2.0. Vagrant-libvirt was resolved to 0.0.1, which depends onĪnother way could be to persuade RubyGems upstream to prefer metadata from locally installed packages instead of the upstream metadata.Īnd the last possibility is to package the vagrant-azure for Fedora. Vagrant-libvirt was resolved to 0.0.9, which depends onīundler could not find compatible versions for gem "ruby-libvirt":įog-libvirt (= 0.3.0) was resolved to 0.3.0, which depends on Just to illustrate the issue, this is what happens during vagrant plugin installation and it might be convincing argument for vagrant-libvirt upstream:īundler could not find compatible versions for gem "nokogiri":įog-xml (= 0.1.2) was resolved to 0.1.2, which depends on One way to fix this would be to ask vagrant upstream to remove the Nokogiri restriction, since it was put in place on the condition, that Vagrant bundles Nokogiri, but this is not true anymore. If it used local metadata from installed packages, it would need to understand, that we modified vagrant-libvirt to support Nokogiri available in Fedora. It appears, that for some reasons, Vagrant (or RubyGems and its resolver) is using upstream metadata to resolve the dependencies. Otherwise, I am afraid I won't be able to help. But I have no idea if vagrant-azure works this way or you encounter another dependency error as soon as you try to use the functionality it implements, since I don't know how to test vagrant-azure. This allows you to install vagrant-azure. # Please note that this ^^ installs just Vagrant, not the group I don't know anything about Ruby and Bundler, but it seems to point at the vagrant-libvirt packaging. Then narrowed it down to the reproducer above. ![]() Worked fine on Fedora 25, then I upgraded the system to Fedora 27, was able to use vagrant with already-installed plugins, but after a month or so I noticed that I can't install new plugins, even if I remove vagrant altogether, delete ~/.vagrant.d and reinstall. ![]() Vagrant-libvirt (> 0), 0.0.9 activated, depends on Which does not match conflicting dependency (= 1.5.10) These errors are usuallyĬaused by misconfigured plugin installations or transient networkĬonflicting dependencies nokogiri (= 1.5.10) and nokogiri (= 1.8.1) sudo dnf install vagrant plugin install vagrant azureīundler, the underlying system Vagrant uses to install plugins, spin up a new Fedora machine (I spin a fedora/27-cloud-base vagrant box)Ģ. Version-Release number of selected component (if applicable): The user plugins don't seem to have a problem to coexist with vageant-libvirt if they are installed - upgrading a system from Fedora 25 passed with no issues (only I was unable to install new plugins) and installing vagrant-libvirt *after* installing the user plugins also works, at least for some plugins. The exact error message depends on the plugin I'm trying to install, but it always seems to do with bundler (the Ruby installer) thinking that the "activated" vagrant-libvirt version is 0.0.9 (where in fact 0.0.40 is installed). Installation of new user vagrant plugins via the "vagrant plugin install xxx" command fails if the vagrant-libvirt package is installed. ![]()
0 Comments
Leave a Reply. |