-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin not compatible with Vagrant 1.6.2 #51
Comments
I'm not sure that the error has anything to do with |
Ooh, I just came across a comment in vagrant-berkshelf issue #186 that leads me to believe this is an issue with |
Here's another issue which specifically mentions the same error you're seeing: berkshelf/vagrant-berkshelf#188. Looks like it's due to a bad monkey patch, but it's not |
Thanks for reporting this and following up. While I don't require |
I have a similar issue that I posted as #55, but I'm not using Berkshelf so I'm unsure how to address the issue. I don't know if upgrading to the newest Vagrant would help, but I've held off for now until some brighter minds can hopefully provide some better advice. |
I haven't gotten this working on 1.6.x yet, only up through 1.5. Will investigate soon. |
I attempted with
|
Just got bit by this issue too. |
Anyone get past this yet? |
Honestly, i just converted to https://github.com/opscode/chef-metal. It leverages the same stuff, but wraps it up all in a fun little package. |
+1 |
+1 |
+1 |
I was able to get past something similar by installing my vagrant plugins in specific order. Vagrant 1.6.3
Someone might want to get the plugin install order a shot? |
This issue is that the i18n A workaround is to modify the i18n slice function to not require all filter keys in the hash
(I've added I've opened an issue on the i18n project and created a PR to resolve this: ruby-i18n/i18n#292 |
Thanks @brettcave, I can confirm that manually patching it works. Do we need to lean on the maintainers of that gem to pull in that PR? It looks like there's a decent backlog of PRs already submitted. |
Couldn't get the repo to vagrant up:
The text was updated successfully, but these errors were encountered: