Closed HughGrant closed 8 years ago
Seems like it's a problem with msgpack bumping to 2.0 and introducing API breaking changes. Pinning to v1.x might temporarily fix this
I guess so
FYI, for those not immediately sure what "pinning to v1.x" translates to in terms of commands, I was able to fix this with
$ brew switch msgpack 1.4.1
Cleaning /usr/local/Cellar/msgpack/1.2.0
Cleaning /usr/local/Cellar/msgpack/1.4.1
Cleaning /usr/local/Cellar/msgpack/2.0.0
7 links created for /usr/local/Cellar/msgpack/1.4.1
Followed by attempting to install neovim-dot-app
again.
But I'm pretty sure that only worked because I already had the 1.4.1 version of msgpack
previously installed. If you are hitting this issue and need to pin, you might try other suggestions from this StackOverflow answer: http://stackoverflow.com/a/4158763/158513
@goodell really nice of you, those who are not familiar with brew commands will benefits from your answer enormously.
@goodell thanks a bunch! I wasn't aware of this API either, went the manual way
I've just merged a PR updating our use of msgpack.
Really surprised you can't tell Homebrew that your project depends on a certain major version of a library.
I'm having this same problem today, and cannot follow @goodell's advice because I have never installed 1.4.1 before. When I try I get:
Error: msgpack does not have a version "1.4.1" in the Cellar.
Versions available: 2.0.0
@isaachess well, if truly desperate you could probably roll back your homebrew version to something from a couple of months ago, install msgpack 1.4.1, then update back to the current homebrew version and execute the brew switch
.
But in my quick test, this also just worked for me, presumably because of @rougal's recent PR:
$ brew update
$ brew upgrade
$ brew install neovim-dot-app --HEAD
Here's the error message