FreeBSD port sysutils/rubygem-bundler updated to 1.7.2 but vagrant requires < 1.7.0

[hxw]

Just updated my FreeBSD system and found that vargant failed because it specifies bundler <1.7.0 in its gemspecc file.

I just changed gemspec to >1.8.0 (on the existing FreeBSD port of 1.6.3) and it appears to work.
At least for a quick check of: up, provision, ssh and halt. (using Ansible as provisioner)

https://github.com/bundler/bundler/blob/1-7-stable/CHANGELOG.md indicates that the 1.7 series is just a security fix from the 1.6.x branch so perhaps vagrant.gemspec can be changed without too much impact.

[bgdnlp]

Confirming, in case confirmation is needed. 'bundler' is at version 1.7.3 now, vagrant doesn't run on FreeBSD because of that.

[sax]

I know that bundler 1.7.0 had some issues, which is why I'm assuming that vagrant's gemspec locks it at < 1.7.0. For our other deployments, we have not had problems with any bundler greater than 1.7.2.

Could the gemspec constraint be updated?

s.add_dependency "bundler", ">= 1.5.2", "!= 1.7.0"

This appears to work for us, though I'm not sure of any unintended side effects.

Confirming the above on a FreeBSD 10.0 system using ruby 2.1.3 and bundler 1.7.3 that ships with rvm. Installed from vagrant source. Big ups! Saved me a headache.

[mitchellh]

Updated the Vagrant dep to 1.7.x. We'll try it out internally for a bit.