Hi, o.k. I found a github wiki entry (went completely under my radar) that explains how to get a vagrant install from dev: https://github.com/mitchellh/vagrant/wiki/Installing-Vagrant-from-source - problem is: it does not work out of the box, if you have a current version of bundle installed as the dev branch of vagrant relies on an old version of bundler. I managed to install the older version in parallel and explicitly call it with "bundle _1.5.2_ install", but "rake install" fails with the same problem and I wasn't able to figure out yet how to tell rake it should use the old version as well.
I updated the WIKI to the point where I got and would appreciate if somebody could help me with the last step. cheers Oliver (went completely under my radar) entry that epxlin On Wednesday, 12 August 2015 11:48:24 UTC+2, Oliver Bestwalter wrote: > > Hello, > > since I am using vagrant with the salt provisioner I noticed quite a few > breakages that could have been caught quite easily had someone actually > exercised the code with some standard settings on the mainstream distros. I > understand that vagrant is a ruby project and that the ruby based > provisioners get more love. It's o.k. I don't complain :) > > As an example: Vagrant + Salt + Windows remains broken for over a year now > ( > https://groups.google.com/forum/#!searchin/vagrant-up/bestwalter/vagrant-up/kY8IVXrKTBA/t5sHKuLSDAUJ > ) > > I would really appreciate some information to help me get started with > testing: > > 1. I am at home in Python and my complete knowledge of Ruby comes from > writing Vagrantfiles, so my capabilites there are still quite limited, but > I would really like to be able to run the development version of vagrant > from my clone on the Linux host, to test fixes and reproduce bugs. I got > the testing to run like described in the README, but I am at sea how to use > the local vagrant clone to spin up boxes. Is there a Howto for people like > me who are not conversant in the ruby ecosystem yet? > > 2. What kind of testing do you have in place to ensure the provisioners > work correctly. Is there something automated in place already? I am pushing > this topic in the salt community to integrate wndows vagrant boxes as part > of testing Windows in Salt development. The other side of the equation > would be to spin up windows vagrant boxes using the different provisioners > with the development branch of Salt to ensure that no regressions creep in. > > 3. How is the release process for vagrant? Do you have roadmaps, release > dates, release candidates? > > thanks > Oliver > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/741d9264-86a1-4227-9715-1b911e32ab24%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
