Homebrew
Homebrew is dead for macOS Catalina and below. #4216
Replies: 6 comments 21 replies
-
They are, php and mariadb depend on newer bottles though. |
Beta Was this translation helpful? Give feedback.
-
|
@SMillerDev - I shall agree to disagree. Homebrew is a friendly solution for selected users. And an unfriendly piece of software for the rest. It is dead for me, and (I am sure) for many others. Good luck for the future of Homebrew, and thanks for your responses :) |
Beta Was this translation helpful? Give feedback.
-
|
You can do the following to revert it back and then install what you wanted, then revert it back again to master or main. Each time something is not supported on Catalina: call this script. #!/bin/bash
#TODO: find all hash supported on Catalina and add them to the array.
COMMIT_HASH=$1
if [ -z "$COMMIT_HASH" ]; then
echo -e "- use git log(not practical) \nvisit https://github.com/Homebrew/homebrew-core/search?q=php&type=commits)"
echo ""
echo ""
printf "provide a commit hash example:f54d39e63b609a2ae25dd039f9edae6c82120f96 not 4ea73eb33aa: "
read COMMIT_HASH
fi
cd /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core/
git reset --hard $COMMIT_HASH
brew update # this is just incase homebrew had a warning about the commit hash that was just reset to.
# verify you have changed HEAD:
brew config
# Core tap origin: https://github.com/Homebrew/homebrew-core
# Core tap HEAD: f54d39e63b609a2ae25dd039f9edae6c82120f96
# Core tap last commit: 3 months ago
# Core tap branch: master
echo "Reverted to commit hash $COMMIT_HASH on $(date)" >> scripts.log
# revert back to master or main.
git checkout master
# finally git pull to last commit again to revert back to current:
cd /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core/
git pull
# HEAD: ba6d87eed9ce31f42fa2b33a4e6067d9cf17f13f
# Last commit: 29 hours ago
# Core tap origin: https://github.com/Homebrew/homebrew-core
# Core tap HEAD: 9f6f46344e65033096b2ba68001ec38467e84a8f
# Core tap last commit: 36 minutes ago
# Core tap branch: masterNow you can do The goal is to find all the Formula that was support for Catalina in the commit history. |
Beta Was this translation helpful? Give feedback.
-
|
If you're going to manually install the latest available version for Catalina you might as well just stop updating. It'll save you a step. |
Beta Was this translation helpful? Give feedback.
-
|
@Nllii - Thank you! I will try this script on my Catalina :) @SMillerDev - If there is a way to manually install all required formula for Catalina to be able to run Laravel Valet I would stop updating those bottles :) So far, I found a solution like so :)
|
Beta Was this translation helpful? Give feedback.
-
|
MacOs Monterey should have no issues(as for now). Lastly, please ask the lovely people at tigerbrew if they have some time to give, in starting a Catalina or Monterey branch https://github.com/mistydemeo/tigerbrew like they did 10 years ago. |
Beta Was this translation helpful? Give feedback.
-
|
Homebrew has always had this policy, it didn't "grow" out of nowhere. |
Beta Was this translation helpful? Give feedback.
-
|
@sroby - my disappointment is not with the policy. It is with the absence of archives for past releases. Which, actually, is a common practice even for Apple. |
Beta Was this translation helpful? Give feedback.
-
|
Homebrew operates as Git repositories. Every change we've ever made is archived that way. |
Beta Was this translation helpful? Give feedback.
-
|
@Bo98 - Really? If all changes you make are archived, please assist me with finding the archives for Catalina bottles. |
Beta Was this translation helpful? Give feedback.
-
|
Its a pain, but you can read the commit history and look for Catalina. |
Beta Was this translation helpful? Give feedback.
-
|
I definitely agree with you on this. I can't use newer macOS versions because I use the Adobe CS6 suits and I can't get off of them because I specifically use Fireworks which only has 32bit. The last supported version of macOS for running 32bit is Mojave. So I'm stuck on Mojave for that reason. PHP 8.1.13 using Homebrew was working for me last week. Then I did an upgrade which then upgraded the dependencies broke my PHP upgrade installation, even though I have another PHP installation on another macOS that's running PHP 8.2 on Mojave as well. So whatever they upgraded for those dependencies are now broken since the last update. I'm currently getting this error now when trying to install PHP's dependencies after it broke from the upgrade. These are the dependencies that are broken and have the same error as the freetype one above.
I can't even go back and compile from source anymore because I don't have those bottles or formulas and can't compile them through Homebrew either. EDIT: Looks like I was able to fix this by going to the working PHP installation with PHP 8.2.1 and take the files from there. So what I did was go into LAST EDIT: I got it to work. So what I did was there were some things actually missing even after I had copied over those dependencies. First thing I was seeing was After finding this out, all I had to do was create the symbolic links because there aren't there when I copied them over. Mind you, this is a fresh macOS installation. So for obvious reasons those symbolic links weren't there. All I did was After that, I kept getting this error when trying to install PHP. So I immediately thought maybe I'm missing libjpeg. I tried installing libjpeg and it turns out, it's actually just the jpeg formula. So I did a So I'm thinking to myself "what is going on? I have libavif already". So I tried to uninstall libavif and tried to reinstall it because I thought maybe the copied down version was having an issue. Got the same error again so I tried uninstalling it once more. Then I got this error After finding that out, I did Shortly after, I found out that I was also missing another link for aom even though I have the files in there and have the symbolic links to the After that, I tried Though this time it gave me more information at the bottom. Turns out, I was missing the link that Homebrew does for all of the dependencies I copied over. So all I needed to do was So in all honesty, if I knew what I was missing, I could have cut down the process a lot more. tl;dr
EDIT: I have uploaded all of the files that I have for Homebrew to this repo. |
Beta Was this translation helpful? Give feedback.
-
|
My suggestion to you would be to use OpenCore Legacy Patcher to install Ventura on your mid-2012 MBP. According to the supported models page all 2012 MBPs are listed as "Everything is supported" so it should work well. |
Beta Was this translation helpful? Give feedback.
-
This isn’t a workaround though. It was supported even up til the error occurred. The reason why it’s no longer working is because the Homebrew team changed something in the configuration files which errored out. The issue isn’t “can I support new software on old hardware”, the issue is “if the Homebrew team breaks something in the configuration files, how can I go back to a working state”. I’m sure this error also occurs on newer versions of macOS as well. The only reason why you guys haven’t ran into it is because the packages aren’t being updated for you or you aren’t using these specific packages that are broken. |
Beta Was this translation helpful? Give feedback.
-
This argument I have quoted from you contradicts the suggestion you gave to GrowYourOwnFreedom. Installing newer macOS versions on “unsupported” hardware has the same issues you’re trying to argue against. Newer macOS versions are “unsupported” on old hardware so there can always be some weird buggy side effect with installing new versions of macOS on old hardware. Especially if you’re using a 3rd party software to flash the new macOS version onto the old hardware and not the proper way of going through the official installer. Lastly, the reason why I don’t agree with your argument is because this is just like situations where people throw out good hardware and buy new hardware because it’s the “hip” thing to do. You do realize you’re throwing out a device that cost you $1,299 in the start right? This is the reason why people rummage through garbage dumpsters, because apparently people have TOO much money to be throwing out good working hardware. That’s like throwing away your $70 K car because it made a “little” noise. Until it’s dead on its knees and it no longer is working, it should still be used or you’ll be wasting your money. Hence why I’m still using old hardware because my hardware is still running perfectly fine. Even more fine than brand spanking new Macs. Lastly, these “workarounds” are only occurring now because the Homebrew team changed something in the files which broke the installation process. Check the error again, if you’re a developer, you’d know that the error relates to a defect the developer of that file did. So it “could” be intentional, but it could also be human error which broke the file. It doesn’t necessarily “have” to be a hardware/“unsupported” issue. |
Beta Was this translation helpful? Give feedback.
-
|
You seem to be conflating two separate situations. There is no contradiction to what I said, GrowYourOwnFreedom has not stated that they need to run an outdated macOS to run old software, and therefore it would make sense for them to use OCLP to install a modern macOS on their old MBP so they can keep using it with current software. Yes, OCLP is not perfect, but in the end it's still a better solution than running an outdated insecure macOS that might not run all current software. |
Beta Was this translation helpful? Give feedback.
-
It is a workaround, as you are on an unsupported OS. The reasoning of "it was working so it was supported" does not hold up. Our install guide states:
We, as volunteer maintainers, have a limited amount of time to work on Homebrew. We utilize this time to develop new features and support the OS's that Apple supports. We do not intentionally and maliciously break compatibility with older systems, but we can no longer devote time to troubleshooting for a subset of users. If something breaks for unsupported OS's through the course of normal development, that's just the way it is. If you check our analytics for the last 90 days you'll see that Mojave represents 0.82% of all installs during that period for users who are sending analytics. That same page will show you almost 94% of those users are on supported OS's. We have to prioritize our time. I do want to say that I appreciate you posting solutions for your issue in this thread so that it can help others. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks!
Kind regards
Jack
…________________________________
From: sroby ***@***.***>
Sent: Wednesday, March 8, 2023 2:43:19 PM
To: Homebrew/discussions ***@***.***>
Cc: GrowYourOwnFreedom ***@***.***>; Comment ***@***.***>
Subject: Re: [Homebrew/discussions] Homebrew is dead for macOS Catalina and below. (Discussion #4216)
My suggestion to you would be to use OpenCore Legacy Patcher to install Ventura on your mid-2012 MBP. According to the supported models page it's listed as "Everything is supported" so it should work well.
https://dortania.github.io/OpenCore-Legacy-Patcher/MODELS.html#macbook-pro
—
Reply to this email directly, view it on GitHub<#4216 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A6FZG3AXVIFXWA4WAUQKP63W3CLIPANCNFSM6AAAAAAU5JVRPA>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
It become truelly "Missing". |
Beta Was this translation helpful? Give feedback.
-
|
I use several different package managers and different OS versions for different things... on my desk right now isa Windows system, an Ubuntu server installation, and a system running MacOSX 10.6.8. Each of these has unique attributes that makes the day go by more smoothly, and makes my life easier. You want to set up and run a server -- use Ubuntu. Anything else is really a make work project. You want to run some custom software to allow your printer to receive and send faxes -- that's a job for a PC and the custom software that comes with the printer from the manufacturer to do that. And for day to day use -- MacOS wins. I have a few systems that run OCLP to upgrade them beyond what Apple allows -- and some of those run homebrew that way. Where I am going with this is -- don't fight the current. Homebrew wants to keep cutting edge on their system version support for many reasons, all of them good reasons, and that has advantages. I have several systems running homebrew for just that reason. Homebrew works great for the current systems. On the other hand, MacPorts has really outstanding support for older OS versions, and intends to keep this support going. I mean -- it's really very good. You can criticize the need for this, but -- there is a need. So if you want to run software on any older systems, look there, rather than fight the wind. It is easy to set up, easy to install, easy to maintain, and supports the older systems (as much as they can be supported, which is pretty good really) all the way back to 10.4 Tiger PPC. Yes, really. It is not really a "ship it if it builds" situation -- things need to work -- but also passing 100% of the test suite is not a criteria for inclusion either, because frankly very little software can do that. Use the tool that is made for the job. |
Beta Was this translation helpful? Give feedback.
-
Output of
brew configCmake, Aom and Doxygen are not installable These are required for PHP and MariaDBOutput of
brew doctorDescription of issue
At least, make previous formuli bottles to be available for downloads.
What used to be a decent add-on to a Mac grew into a non-backward compatible software.
Beta Was this translation helpful? Give feedback.
All reactions