-
-
Notifications
You must be signed in to change notification settings - Fork 12.9k
Fix makepkg on macOS by adding an older version of fakeroot #229375
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
base: main
Are you sure you want to change the base?
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. |
I am unable to understand whats wrong with commit style here |
tap syntax also seems to be false positive error |
Is this issue reported upstream? Because that should be done before we merge this. |
|
So it seems nobody ever reported it, could you do that? |
I can have a look. Working with Debian devs is a PITA tbh. Anyways, till it's fixed, what shall be the options? |
It is not. The |
Ah thanks for noticing. Fixed. |
I looked into this, and this requires me to have an installation of Debian to file a bug report. Honestly its too much of a hassle that I'd rather bisect the faulty commit. |
Fakeroot starting from version 1.35 hangs on macOS and has not been fixed for a long time. Add the older supported version 1.31 formula for macOS users
makepkg needs fakeroot to work. On macOS, the version of fakeroot working atm is 1.31, which is not the latest version. This commit makes makepkg depend on fakeroot@1.31 on macOS
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I looked into this, and this requires me to have an installation of Debian to file a bug report. Honestly its too much of a hassle that I'd rather bisect the faulty commit.
I'm afraid we'll have to wait until this is reported to Debian before we merge this. You don't have to be the one to do it, but someone has to before we apply this workaround here, or else we risk just carrying this workaround indefinitely.
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>
?