Update to Vagrant 1.2.2 and vagrant-vbguest 0.8#1
Open
dergachev wants to merge 2 commits intodotless-de:masterfrom
Open
Update to Vagrant 1.2.2 and vagrant-vbguest 0.8#1dergachev wants to merge 2 commits intodotless-de:masterfrom
dergachev wants to merge 2 commits intodotless-de:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
At the moment, vagrant-plugins-env repo includes vagrant 1.1.3 as a submodule:
This version of Vagrant seems to throw the following bug, at least when using with precise64:
This bug seems to be specific to Vagrant 1.3, and is resolved by upgrading. See hashicorp/vagrant#1502
For me, the following was required to change the submodule reference:
Testing it, I realized I needed to update vagrant-vbguest too:
To do this:
To test: