-
-
Notifications
You must be signed in to change notification settings - Fork 10.6k
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 style error #43898
Comments
This ended up being a bit of a problem... I removed my ruby installs (except system) and installed After a bit of tinkering with
to
and then running
This seems to have recreated the original 2.3.0 directory at the above path... so I just removed the 2.3.0-old directory and things seem to be going alright. |
Closing since it was solved. |
Looks like running
|
@commitay the inferred problem being that The man page would back this up...
|
Yeah, it was working a couple of weeks ago. |
@CryoRenegade I believe you're getting this error because there is no cask named Just so you know @commitay, I can reproduce your issue with running |
Works for me:
|
Clean VM, new install of Homebrew on master:
@reitermarkus Do you have another |
Tried this on my own machine and on a VM. VM:
non-VM:
|
I've a similar issue running
Output of
I've brew ruby installed too:
|
I seem to solved mine doing:
or
or (fish-shell way)
And last running Either way, I managed to make mine working again. Needed to solve this so I could run |
Well, I found that don't have a Doing some researching and reading through those issues Homebrew/brew#3760, Homebrew/brew#3781, Homebrew/brew#3736. I decided to go back to this version of utils.rb file, right before those changes to However running
I don't know much about ruby/gem, however I tried to add helpful info as much as I can. Mentioning @MikeMcQuaid since he is the owner of those commits. |
Homebrew uses system ruby or its own portable ruby if system ruby is to old.
I'd recommend not doing this.
@abdelrahmanrifai Please open a new issue for this. |
Closing as the original user issue was resolved.
|
General troubleshooting steps
--force
and the issue is still present.brew update-reset && brew update
and retried my command.brew doctor
, fixed as many issues as possible and retried my command.Description of issue
Issue discovered while trying to run @vitorgalvao's
cask-repair
(getting red dot error outputs).Output of your command with
--verbose --debug
Output of
brew cask doctor
What is interesting is that after I started experiencing this issue I tried to
brew rm ruby@2.3
(which is what I had installed) andbrew install ruby
which got me to ruby 2.5. However the$LOAD_PATH
in homebrew still has a bunch of 2.3.3 paths...When I previously had a problem with
cask-repair
there wasgem
command for removingrubocop
andrubocop-cask
which I tried again, but they were already removed and the gems were gone from~/.gem
and the subdirs. It was after this that I tried to upgrade ruby.Help appreciated in getting
brew cask style
(and by extensioncask-repair
) working again!The text was updated successfully, but these errors were encountered: