-
Notifications
You must be signed in to change notification settings - Fork 2
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
LoadError: cannot load such file -- search/overrides #35
Comments
Having the same issue https://gist.github.com/kylesloan/5880457 |
Unfortunately the cookbook on the community site is not usable due to a Chef bug/restriction. You need to configure Berkshelf to download it from Github. So put to Berksfile something like: cookbook 'chef-solo-search', github: 'edelight/chef-solo-search', ref: '0.4.0' |
What a chore! Still not having much luck: Samuels-MacBook-Pro-2:api samuelrichardson (master) $ berks update chef-solo-search Samuels-MacBook-Pro-2:api samuelrichardson (master) $ vagrant provision |
@Rodeoclash that might be related to berkshelf/vagrant-berkshelf#17 Or maybe the broken 0.4.0 version was still cached. You can nuke it with |
Good call on the cache, I blew that away and vagrant up/provision and everything worked fine. Still new to this so thanks for the help! |
I have I also upgraded my chef-client to |
Just a wild guess but maybe the Berksfile.lock has old reference? Anyway this seems more of a Berkshelf issue than chef-solo-search issue. |
Thanks a lot. That was the one thing I overlooked! |
I might be missing something obvious here (I'm follow instructions from http://blog.atwam.com/blog/2013/06/10/configuring-chef-solo-for-our-servers/)
Adding the cookbook (via Berksfile)
cookbook 'chef-solo-search'
Results in the error
LoadError: cannot load such file -- search/overrides
When I try to provision using vagrant. I've followed the instructions and the additional details in ticket 8 (including copying the search.rb and parser.rb files into a dummy cookbook) but it does not make any difference.
Any ideas?
The text was updated successfully, but these errors were encountered: