-
-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
Formula dependency incorrectly marked as installed_on_request
upon upgrade/migration
#18754
Comments
Did you do a targeted upgrade, i.e. If all you did was Anyway, the workaround: |
It seems that a plain
|
That seems like a bug to me. In fact, as I mentioned elsewhere, it's puzzling that anything but the original formula install (requested or dependency) should automatically change those flags. Surely the fact that |
@ZhongRuoyu seems like a bug with the alias migration stuff for
Increasingly I wonder if
|
Just
I don't think that is enough to avoid it in (As for my case I corrected the fields in |
I guess trying to find old Keg fails as new directory doesn't exist on filesystem for formula-to-alias as opposed to rename migrator brew/Library/Homebrew/upgrade.rb Lines 135 to 137 in 7981369
So brew/Library/Homebrew/upgrade.rb Line 151 in 7981369
|
brew doctor
outputVerification
brew doctor
output" above saysYour system is ready to brew.
and am still able to reproduce my issue.brew update
twice and am still able to reproduce my issue.brew install wget
. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.brew config
outputWhat were you trying to do (and why)?
pkg-config
was installed as a dependency ofrust
on my machine. Homebrew/homebrew-core#194885 replacedpkg-config
withpkgconf
, and after upgrading and doingbrew bundle dump
, I noticedpkgconf
now becomes part of the generated Brewfile, which it probably shouldn't:What happened (include all command output)?
After investigation it turns out
pkgconf
is somehow marked asinstalled_on_request
after upgrading:What did you expect to happen?
Compared to a normal dependency:
Step-by-step reproduction instructions (by running
brew
commands)The text was updated successfully, but these errors were encountered: