-
-
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
How Do I Fix/Silence "Use new_tap/xxx instead of deprecated old_tap/xxx" Warnings? #1459
Comments
Thanks for the report. This is a bug and I'll work on a fix. |
For now a |
I know it's going to void my warranty, but my hackish workaround was just to 'sed' the corresponding I |
@DabeDotCom No worries, that's probably a sensible approach if you want to avoid reinstalling. Thanks! |
PR opened in #1485. |
I have a question...
After ce2b11f/#1371 went in,
brew outdated
(as well asbrew uses --installed <formula>
and maybe others) started spitting out a handful of, e.g.messages — which I understand is to allow third-party taps to migrate formulae into and out of core... (And yes, I'm heavily in favor of future-proofing!)
My problem, though, is: What do I have to do to "use" the new location instead? These formulae have been installed (and working fine!) forever...
brew info
seems happy with the status quo:Do I have to manually install all these apps from the new, fully-scoped locations? When I try that,
brew install
andbrew upgrade
claim everything is already up-to-date:So does that mean I have to uninstall the existing versions, first? (More importantly: SHOULD I have to?!)
Given that I didn't actually /explicitly/ list those formula names when running
brew outdated
, the fact that there's no clear instructions about how to rectify the situation makes these messages a little Less Than Awesome, IMHO. :-\The text was updated successfully, but these errors were encountered: