I am not an early adopter.
Until last week, I was running 10.7. Yes, it’s true. Don’t judge. I had code to ship. No time for yak shaving!
But finally I bit the bullet. After dual redundant spatially-distributed backups, I ran the upgrade. And everything went great at the GUI level! And the Messages app is awesome! But Ruby, virtualenv, and Java were all borked. I don’t even Ruby, but I use Octopress and Heroku, so I couldn’t even blog or restart Hubot. Sadness!
Some tips in your upgrade:
Homebrew links will probably be messed up.
brew unlink fooand then
brew link foofixed most of these. Consider scripting it to save time and heartache! E.G.
for i in $( brew list ); do brew unlink $i; brew link $i; done
Ruby has a new version, and RVM is now using
.rvmrcto keep track of Ruby versions. It automatically moved these files around without telling me, which is half of what broke my blog.
Ruby 2.whatever will complain about Readlines or Yaml or OpenSSL depending on its mood. Try uninstalling Ruby with RVM, installing whatever it demands, and then reinstalling Ruby and seeing if it works. At this point, I’m basically thinking of Ruby as a demanding newborn that is astonishingly articulate about its needs.
Java is gone because reasons. Here’s how to reinstall it.
I’m still not sure what’s going on with my virtualenv but I think it has to do with my questionable decision to use a third-party Python distro. Passing in a path to the system Python with
-pseems to be a decent workaround.
A bunch of packages wouldn’t install through pip, and it turns out that the new default when flags are not recognized by gcc is to CATASTROPHICALLY CRASH rather than keep calm and carry on. Don’t have time for this drama? Add the following to your environment:
Back to work!