Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to install brew-cask v0.53.3, Error: No such file or directory - brew-cask #9807

Closed
vinnyang opened this issue Feb 27, 2015 · 8 comments

Comments

@vinnyang
Copy link

brew-cask just suddenly stopped working…

Error: No such file or directory - brew-cask

I tried re-installing brew-cask, and even homebrew itself, but after all that I am still getting this same error:

screen shot 2015-02-27 at 4 30 08 pm

Please let me know what other info I can provide to help debug this.
Thanks in advance!

@phinze
Copy link
Contributor

phinze commented Feb 27, 2015

That's not good!

Thanks for the report... feels upstreamy... going to try repro locally. Stand by!

@phinze
Copy link
Contributor

phinze commented Feb 27, 2015

Ok I verified sanity locally, so let's see what's going on over on your side. Can you check to see if your executable works if you address it directly?

/usr/local/Cellar/brew-cask/0.53.3/bin/brew-cask

@vinnyang
Copy link
Author

This is what I got…

 $ /usr/local/Cellar/brew-cask/0.53.3/bin/brew-cask
 zsh: /usr/local/Cellar/brew-cask/0.53.3/bin/brew-cask: bad interpreter: /bin/bash^M: no such file or directory

my zsh version:

zsh 5.0.2 (x86_64-apple-darwin13.0)

and, running that inside iTerm2.

@vinnyang
Copy link
Author

Not sure where it got the /bin/bash^M from, however /bin/bash is actually there and I believe it is the bash-3.2 that comes with my version of OS X

@phinze
Copy link
Contributor

phinze commented Feb 27, 2015

Hmmm .... sounds like git might be configured to clone things with windows line endings?

Can you move your ~/.gitconfig out of the way and retry?

@vinnyang
Copy link
Author

screen shot 2015-02-27 at 6 02 22 pm

😞

@phinze
Copy link
Contributor

phinze commented Feb 28, 2015

Dang! So weird! 😞

Well you can manually repair that executable by removing the ^M character(s) from it.

I still suspect it's git related - you could try to see if there are any other git configs sneaking line ending settings in there. A good starting point on learning about git's line-ending support is here: https://help.github.com/articles/dealing-with-line-endings/

@vinnyang
Copy link
Author

vinnyang commented Mar 2, 2015

Thanks! Changing the EOL characters in that executable fixed the issue for me, but surely this is a very weird issue.

@vinnyang vinnyang closed this as completed Mar 2, 2015
@Homebrew Homebrew locked and limited conversation to collaborators May 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants