-
-
Notifications
You must be signed in to change notification settings - Fork 10k
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
autoremove detects package that is needed and cannot be removed #13729
Comments
It looks like the autoremove logic tags a formula as fit for being removed and then later on another check decides that it isn't. The solution here would be to probably use the same logic in both places or update the autoremove logic to better detect when a package is fit to be removed. More specifically, the I was only able to reproduce the error message when I adding export HOMEBREW_NO_CLEANUP_FORMULAE=mactex,ghostscript In that case, there seems to be an error with ignoring those no cleanup formulae during the autoremove process. |
I think what actually is happening here is that If this is correct, then this is related to #13717. |
Actually, I suspect |
What's the output of brew ruby -e 'puts Tab.for_formula(:openjpeg.f).runtime_dependencies' ? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
brew config
outputbrew doctor
outputVerification
brew update
and am still able to reproduce my issue.brew doctor
and that did not fix my problem.What were you trying to do (and why)?
Trying to clean up no longer used packages with
autoremove
and then the command tries to remove needed packagejpeg
that some safety check catches and refuses to remove.Current installed formulas:
What happened (include all command output)?
openjpeg
is brought in bymactex
andghostscript
What did you expect to happen?
That
autoremove
does not suggest packages that cannot be removed which results in an error. The main problem with this error is that it preventsautoremove
from working at all since it seems to require atomic operations (which in other circumstances is probably a good thing).Even if there are 50 other packages that can safely be removed it is impossible to use
autoremove
Step-by-step reproduction instructions (by running
brew
commands)1. `brew autoremove`
The text was updated successfully, but these errors were encountered: