OS X sed doesn't understand '\s', even in extended mode. ??
A release log message wrongly referred to a remote repo.
Run the specs via binstubs.
Merge branch 'release'
v0.18.0 - A --debug bug, and nodejs, debian, & pacman improvements.

- Fixed an issue where shell commands' output was being corrupted by
  the use of --debug (see 7f78bbe).

- (Tim Riley) Fixed NpmHelper.should_sudo? under nodenv. Previously
  it was requiring sudo because the global installation wasn't
  writable, even when nodenv meant a local, writable location would
  be used.

- Made sure /usr/bin/node is available on apt boxes. The binary was
  renamed upstream.
  https://lists.debian.org/debian-devel-announce/2012/07/msg00002.html

- Fixed debian version parsing so that different versions of the same
  release are understood as such, instead of as separate releases.
  (Thanks to schnittchen for reporting this and for the quick-fix
  patches in the meantime.)

- Added automatic package list updating to PacmanHelper.

- By default, parallelize builds in the 'src' template according to
  the cpu count.

- Removed an attempt to avoid double-updating in the 'apt source'
  deps, that meant updating could be skipped altogether under certain
  conditions.

- Added the definition for ubuntu 14.04 'trusty'.
Confirm the supplied ref is valid in GitRepo#resolve[_full].

The '^{commit}' suffix causes rev-parse to check the ref resolves to
a commit, and not just that it's a valid-looking ref. Without it, any
40-character SHA will be resolved to itself, and appear to exist in
the repo.
Make the 'multiple installations' log message a bit clearer.

Answering 'y' at this prompt says "yes, attempt to meet the dep", not
"yes, consider it met".

That is, the choice is between attempting to continue as normal and
bailing out immediately, not whether or not to bypass this dep's
normal logic.