-
Notifications
You must be signed in to change notification settings - Fork 122
Fix important recipes that don't run under mavericks #149
Comments
This is making Sprout sort of useless on all the new machines we buy. We put a bounty out on it so hopefully it can get some attention: https://www.bountysource.com/issues/1215590-fix-import-recipes-that-don-t-run-under-mavericks |
Are you able to leave out the recipes that don't work under Mavericks for I'll aim to send a longer update about Mavericks support to the In the interim, here's a brief outline of the approach we'll be taking:
Sprout has some recipes from the ~Leopard era, we're taking this Like its predecessor, Sprout will only support one version of OSX at a Thanks for posting the bounty, any help in line with the outline I've just Hope this information helps you get a little closer to getting your new On Tuesday, November 19, 2013, Gust wrote:
tiny keyboard + fat fingers |
And then it worked:
|
Yes, the postgresql installation does in fact work after the second install. It seems like the directory |
I'm not entirely sure what is wrong with RVM, but am trying to fix it. Is it installing ruby-2.0.0-p247 that is broken? |
@hiremaga there was broken ruby-2.0.0 binary but it has been removed and also ruby version was bumped, please try again and if it fails again let me know about the problems you face |
You're right! |
The current script for postgres doesn't seem to work for a new machine. |
These recipes need to be fixed for mavericks
The text was updated successfully, but these errors were encountered: