-
-
Notifications
You must be signed in to change notification settings - Fork 9.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 tap fails with git-lfs installed #4988
Labels
outdated
PR was locked due to age
Comments
You have configured all repositories to use |
@MikeMcQuaid thanks, it worked! git-lfs is a trap, because it recommends |
If anyone ever finds this useful - just try:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Please note we will close your issue without comment if you delete, do not read or do not fill out the issue checklist below and provide ALL the requested information. If you repeatedly fail to use the issue template, we will block you from ever submitting issues to Homebrew again.
brew
command and reproduced the problem with multiple formulae? If it's a problem with a single, official formula (not cask) please file this issue at Homebrew/homebrew-core: https://github.com/Homebrew/homebrew-core/issues/new/choose. If it's abrew cask
problem please file this issue at https://github.com/Homebrew/homebrew-cask/issues/new/choose. If it's a tap (e.g. Homebrew/homebrew-php) problem please file this issue at the tap.brew update
and can still reproduce the problem?brew doctor
, fixed all issues and can still reproduce the problem?brew config
andbrew doctor
and included their output with your issue?brew config
brew doctor
- the Homebrew/homebrew-core is at stable branch, and doctor complains... Is it OK?I've installed git-lfs via
brew install git-lfs
and get problems withbrew tap
command after that.The problem reproduces with any tap.
And even
brew update
prints a warning.git-lfs
exists in my $PATHWhat am I doing wrong? :)
The text was updated successfully, but these errors were encountered: