-
-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
statesmith 0.17.4 (new formula) #207657
base: master
Are you sure you want to change the base?
statesmith 0.17.4 (new formula) #207657
Conversation
Thanks for contributing to Homebrew! 🎉 It looks like you're having trouble with a CI failure. See our contribution guide for help. You may be most interested in the section on dealing with CI failures. You can find the CI logs in the Checks tab of your pull request. |
Hm, have y'all see this before? Looks like there's a return in
Running on my own mac osx 15 doesn't seem to have this problem
|
The "Application <CR><LF>Support" problem seems to be specific to the If I run the exact same binary in my shell it works fine, but if I run it from
It doesn't seem to be a problem with ruby, just with brew. If I make the same call from a test ruby script using system, it works fine:
|
Is there a way to enable |
No, we very explicitly sandbox everything in a formula test to a tmp directory. |
For posterity: the CRLF symptom is confirmed as a red herring. The real problem was that the brew sandbox was preventing writes to the |
HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>
, where<formula>
is the name of the formula you're submitting?brew test <formula>
, where<formula>
is the name of the formula you're submitting?brew audit --strict <formula>
(after doingHOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>
)? If this is a new formula, does it passbrew audit --new <formula>
?