Hi Anton, I am still unable to install vagrant from source due to a bundler versioning issue.
I opened an issue for that now: https://github.com/mitchellh/vagrant/issues/6183 The Ruby ecosystem is a bit of a mystery to me, so I hope somebody will chip in and update the docs. cheers Oliver On Mon, 24 Aug 2015 at 18:51 AD. <[email protected]> wrote: > Hi Oliver, > > I'm in a similar boat :) > > I'm just now picking up a partially completed project of mine that's been > shelved since last year and have run into plenty of regressions and plain > old changes as I bring the various components up to date. There's a lot of > moving parts. > > eg: Vagrant 1.6.x -> 1.7.x, Packer 0.6.x -> 0.8.x, Salt 2014.1 -> 2015.x, > Ubuntu 12.04 -> 14.04, and Windows 2008R2 -> 2012R2. And moving the Windows > communicators from cygwin SSH/Bash to WinRM/Powershell. Things would be > much easier without Windows that's for sure. > > Although I'm not a devloper, I'm ok with Python. My only tiny Ruby > experience though is (ironically I suppose) submitting a minor vagrant salt > provisioner (on Windows) fix last year. I suspect Packer will be sending me > to the Go tutorial too. > > I'll look through your Trello board to see if I can help out anywhere. > > Cheers > Anton > > On Wednesday, 12 August 2015 21:48:24 UTC+12, 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 a topic in the > Google Groups "Vagrant" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/vagrant-up/2vBhQMYsqn4/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/vagrant-up/405eb91d-006e-4539-ba51-5cc324db2d39%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/405eb91d-006e-4539-ba51-5cc324db2d39%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAG5CgtrOQrj_m6z%2BatWBMRRTCpZpiBvhgfZHOS7C4sBD%2ByugVw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
