Closed johntdyer closed 11 years ago
I think I talked to you in IRC?
Anyways, the fix is to gem uninstall vagrant
and then use the installer. ActiveSupport is screwing you up.
Yea, this is still an issue for me because a gem I am using pulls in Vagrant every time I run bundler. Still trying to work that out
I'm having the same problem. I'm trying to use Berkshelf RC1 with Vagrant and the documented Berkshelf workflow wants to use the vagrant gem.
bundle install bundle exec vagrant up
...which installs the Vagrant 1.0.5 gem. Is this an activesupport problem or can vagrant be patched to fix this or ??
I think I understand the problem better now. Its an issue with Berkshelf using ActiveSupport which they already fixed.
@mitchellh why are you suggesting that users do not install Vagrant by gem?
Berkshelf is a dependency resolver for Chef and it integrates with Vagrant by an included plugin. We have a dependency on Vagrant to ensure that the plugin is running against a known version of Vagrant and installing by installer would mean this dependency would no longer be pinned.
any idea what this is about? I get it when I run
The basic exception is as follows:
My VagrantFile is:
The full failure logs can be found below: https://gist.github.com/cf3d2f612c7d18bfab11