El Capitan update: Ruby, Rails, homebrew, VirtualBox/Vagrant, Elixir etc.

el_capitan.md

My notes from updating to El Capitan, as a Ruby/Rails developer working in VirtualBox/Vagrant.

VirtualBox and Vagrant

Our dev environment currently requires us to use older versions of VirtualBox (4.3) and Vagrant (1.7.1).

It seems the new "SIP" protection messes with that version of VirtualBox.

I tried upgrading VirtualBox (to 5.0.6) and Vagrant (to 1.7.4). Those seemed to run fine on El Capitan, but we rely on Chef v. 10 and Vagrant doesn't seem to get along with it (error: "invalid option: --force-formatter").

So I ended up simply turning off the SIP protection and using VirtualBox 4.3 and Vagrant 1.7.1.

A co-worker had to turn off SIP and reinstall VirtualBox 4.3 (download link) for it to work. I also reinstalled it, indirectly, since I upgraded and then downgraded.

Before he reinstalled it, he got errors like:

==> default: Clearing any previously set network interfaces...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["hostonlyif", "create"]

Stderr: 0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
…

Homebrew

brew doctor reported some issues, and some additional issues after those were fixed.

I basically did what it says about Homebrew here.

Fixing /usr/local ownership:

sudo chown -R $(whoami):admin /usr/local

Fixing broken symlinks:

brew prune

It said "xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun". Fixed by reinstalling the Xcode command-line tools:

xcode-select --install
# And then follow instructions

brew doctor also said "You have unlinked kegs in your Cellar …" with some instructions, which I followed:

brew link ossp-uuid ppl011

It also complained about "Unbrewed dylibs", which I ignored, assuming it was something installed outside homebrew and that it wouldn't cause issues. We'll see.

reattach-to-user-namespace

I use reattach-to-user-namespace so the OS X pasteboard works inside tmux.

Opening a tmux session gave me "warning: reattach-to-user-namespace: unsupported new OS, trying as if it were 10.10". Went away when I upgraded the tool to version 2.4:

 brew upgrade reattach-to-user-namespace

Doesn't seem to work fully though – have yet to investigate that.

Seems to just work

• RVM
• Ruby, Rails, Sinatra
• Elixir
• Pow (maybe because I turned SIP off?)

This helped me. Thanks, @henrik!

@kriskhaira Thank you so much for letting me know! :)

@henrik Do you still need reattach-to-user-namespace?

From their README

Note: Under Yosemite (and later) pasteboard access seems to work fine without the program from this repository.

(Note: I don't use pbcopy and pbpaste that often so I'm not a user of reattach-to-user-namespace myself)

A cursory test without reattach-to-user-namespace worked for me with pbcopy and pbpaste with El Capitan upgrade so removing this from my .tmux.conf.

This was successful in eliminating the "warning: reattach-to-user-namespace: unsupported new OS, trying as if it were 10.10" after upgrading to High Sierra. Thank you for posting this.