New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.9.4 installs very old version of plugin #8550
Comments
@kivoli Forcing the latest version ( |
@chrisroberts Okay, but I find the behaviour of Vagrant a bit confusing, too. Because it insisted on |
Please support libvirt right oob, this is the best virtualization option on Linux systems and it sux that vagrant still produces problems with that. It would help if your devs used Linux systems, then these kind of errors would never happen. |
Removes the nokogiri dependency to prevent resolution conflicts with plugins that may require earlier or later versions than what Vagrant constrains to. Fixes hashicorp#8550
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
For an unknown reason Vagrant 1.9.4 reproducible installs only a very old version of vagrant-libvirt (0.0.20) while 1.9.3 does pull the correct version, 0.0.40. Downgrading Vagrant for this purpose works, too.
Vagrant version
Host operating system
Ubuntu 16.04
Guest operating system
N/A
Vagrantfile
N/A
Debug output
Expected behavior
Install newest version (0.0.40) of
vagrant-libvirt
plugin.Actual behavior
Installs very old version (0.0.20)
Steps to reproduce
vagrant plugin install vagrant-libvirt
The text was updated successfully, but these errors were encountered: