Closed stweil closed 2 years ago
As the upgrade works nevertheless, this is only a cosmetic problem (wrong version in log message). That's why I did not report it up to now.
I was able to reproduce this:
brew install pango
brew upgrade
In this situation, both pango
and its dependency, harbuzz
, are outdated and will be upgraded by brew upgrade
.
I think it shows up differently because it's an outdated dependency. Here, the top-level formula we're trying to upgrade is pango
but, of course, we'll upgrade harfbuzz
too in the process. Somewhere we must be using the wrong version variable in the log message only in this particular case.
Interestingly, brew upgrade pango
in step 4 doesn't seem to have the same problem. I think this is because the logging is different when there's only one top-level formula to upgrade. Running brew upgrade pango harfbuzz
does show the issue. In other words, the issue seems to be present when an upgrade was requested for a formula either directly or with a catch-all brew upgrade
and that formula is a dependency of another outdated formula that will also be upgraded.
@FnControlOption this is another one that I'm sure isn't related to your changes but if you were able to take a look we'd be super grateful ❤️
brew config
outputbrew doctor
outputbrew 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)?
I run
brew upgrade
from time to time for obvious reasons.What happened (include all command output)?
What did you expect to happen?
I expect correct log messages, but get for example
instead of
Many messages show the correct versions, but I observe wrong upgrade messages (always looking like x.y.z -> x.y.z, so claiming that there was no release change) since a long time on different Mac hosts (both Intel and M1).
Step-by-step reproduction instructions (by running
brew
commands)