lmod/lau issue after Tahoe install and brew upgrade #6735
Unanswered
unixwizard107
asked this question in
Everyday usage
Replies: 1 comment 2 replies
-
|
I'm guessing you hit the 15 hour interval where
For anyone else who sees this, a The issue happened due to a bug in detecting dependent formulae where |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Output of
brew configOutput of
brew doctorDescription of issue
lua: version mismatch: app. needs 504.0, Lua core provides 505.0After I did a an upgrade to Tahoe, I ran:
brew update --verbose && brew outdated --verbose && brew upgrade --greedy --verbose && mas upgrade && brew cleanup --verbose ; brew doctor; tea --sync -nBut when I then tried to run a couple of programs that were using TACC's lmod to set up an environment, which in turn called lua(1). I started to see the failure listed above. I did some internet searching and discovered that in 2020, there was a similar issue between 5.03 and 5.04.
The strange part for me is that I had all three of 5.3, 5.4 and 5.5 installed:
"carlocab: suggested running this command to fix the issue at that time:
HOMEBREW_NO_AUTO_UPDATE=1 brew install -s lmodwhich resulted in:
This seems to have fixed the issue. But I wanted to at least document it, as I suspect that something in the update/upgrade logic is not working quite as intended, and to note it for the maintainers.
Or, if I did something wrong and will amd headed for a different issue, please let me know what the correct way to repair this.
Thanks,
Beta Was this translation helpful? Give feedback.
All reactions