-
-
Notifications
You must be signed in to change notification settings - Fork 296
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
Error: private method `system' called for module Homebrew #1413
Comments
i'm not able to reproduce this on a fresh install. is there anything else about your local setup that would help diagnose this? failing this, you may want to try a reinstall of Homebrew in case something has gone astray there. |
@P4sca1 Hi! I had a same problem on homebrew version |
I upgraded homebrew to |
I see this issue on HEAD, downgrading to 4.3.10 fixes it |
@johng I'm on |
From a clean brew installation I run into it.
Also have seen this on our CI and had to pin to 4.3.10 |
Apologies @johng, still can't reproduce this locally but will try with your instructions when I get a bit. |
I'm getting an error about
|
Thanks!
…On Fri, 26 Jul 2024 at 21:02, Mike McQuaid ***@***.***> wrote:
Closed #1413 <#1413> as
completed via Homebrew/brew#17879
<Homebrew/brew#17879>.
—
Reply to this email directly, view it on GitHub
<#1413 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAUQFJBR5PNE44J3KN5VVO3ZOKML5AVCNFSM6AAAAABLCVCOQSVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTGY3DIOBTGUZDKNY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
brew config
Verification
brew doctor
output saysYour system is ready to brew.
and am still able to reproduce my issue.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)?
Installing multiple packages using
brew bundle
What happened (include all command output)?
What did you expect to happen?
The install should succeed.
Step-by-step reproduction instructions (by running
brew
commands)The issue also occurs when running `brew bundle` without any arguments.
The text was updated successfully, but these errors were encountered: