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
brew cask upgrade fails with "No Cask with this name exists" #101136
Comments
If you’ve opened an issue just to vent, I’d recommend you open a PR instead. You’re welcome to use Homebrew without any guarantees, expressed or implied, but not to demand or expect free work from our volunteer efforts.
Yes, we know it’s frustrating; we don’t want this behaviour either and there’s already another issue open for this. Please search before opening issues; there aren’t that many. |
Hey. I'm sorry for having a bit of a vent. Long day, and frustrating when stuff like this breaks badly :-( The reason I didn't find the open issue you just linked to was because when I googled the particular error messages, all the top suggestions that came up were like the one I linked to above — closed — and without any indication or suggestion of the current open issue's existence, or suggested workarounds or fixes. If the open issue had been linked to in the issues I found — where you replied closing them — I would have realised there was no point in opening a new issue! If you would be able to post a recommended workaround, resolution, or temporary fix (no matter how ugly) in closing issues like this, it will probably help people who discover it through google in future again! Really appreciate it. Thank you :-) Martin |
--force
.brew update-reset && brew update
and retried my command.brew doctor
, fixed as many issues as possible and retried my command.Description of issue
So, identical to the issue described in this issue I've had my whole brew setup mostly made unusable by a series of old casks that have since been removed. I have had to manually remove the contents of the old casks from my file system, as not doing so left me with
brew
completely unusable.I was trying to
brew untap homebrew/homebrew-science --force
but this just got blocked on old casks, e.g.Error: Cask 'mailbox' is unavailable: No Cask with this name exists.
Come on! As you you say in the other issue (linked above) this is "suboptimal" (seriously?!) — this screwed over my whole homebrew install.
brew update-reset && brew update
fails because it gets stuck on the old homebrew-science cask, which I was trying to remove...:Any attempts at
brew doctor
then fail, being blocked by e.g.and
...but I had to do this about 10 times.
If a cask doesn't exist, you can't just block all use of homebrew! 😢
Command that failed
All of them
Output of command with
--verbose --debug
Output of
brew doctor --verbose
Output of
brew tap
The text was updated successfully, but these errors were encountered: