You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a clean system (desktop that had never had ruby, chef or vagrant installed before, but did have virtualbox)
I was able to get a box up, but most of the things it was supposed to install never got up, due to the error
"FATAL: Chef::Exceptions::CookbookNotFound: Cookbook build-essential not found. If you're loading build-essential from another cookbook, make sure you configure the dependency in your metadata"
Hmm, interesting. When I made this, I tested it on a relatively clean installation of OS X and it ran fine, so maybe something has changed in the mean time. May I ask what OS you're running? Thanks
OSX Lion.
It seems that two of the other (current) cookbooks call those in. that may have been a recent change on their part.
I dunno if Chef is magically aware of other 'standard' cookbooks that may be elsewhere on your system, but my machine certifiably had never head of them before.
BTW ... I've taken your code and converted it fully to a silverstripe build-on-the-server recipe last night. I can now do without the provision.sh altogether and get it to pull the current working tarball onto the target machine. Parameterized and templated the db config file as well. Meaning this repo no longer contains all of silverstripe etc.
I'm working on adding a composer-based checkout as an alternate method also. Just as a learning experience, considering I'd never touched ruby, silverstripe, chef or things before. :-)
On a clean system (desktop that had never had ruby, chef or vagrant installed before, but did have virtualbox)
I was able to get a box up, but most of the things it was supposed to install never got up, due to the error
"FATAL: Chef::Exceptions::CookbookNotFound: Cookbook build-essential not found. If you're loading build-essential from another cookbook, make sure you configure the dependency in your metadata"
.. after learning a LOT about the internals of what vagrant and chef was really doing, I was able to go into the 'cookbooks' directory and
git clone https://github.com/opscode-cookbooks/build-essential.git
git clone https://github.com/opscode-cookbooks/xml.git
then run
vagrant provision
and get a lot further than last time.
... Right to the end in fact!
I believe these two libraries should be added as submodules in the cookbooks directory.
The text was updated successfully, but these errors were encountered: