14 ms·
So it goes... Warning: You are using macOS 11. We (and Apple) do not provide support for this old version. It is expected behaviour that some formulae wi
by cglong 3y ago
So it goes...
Warning: You are using macOS 11.
We (and Apple) do not provide support for this old version.
It is expected behaviour that some formulae will fail to build in this old version.
It is expected behaviour that Homebrew will be buggy and slow.
Do not create any issues about this on Homebrew's GitHub repositories.
Do not create any issues even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from Homebrew or its maintainers on social media.
You may ask for help in Homebrew's discussions but are unlikely to receive a response.
Try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.
- m463 3y agoexport HOMEBREW_NO_ANALYTICS=1
- joeman1000 3y agoTime to move to MacPorts.
- esafak 3y agoDon't move today, because the Sonoma release is not out yet. https://www.macports.org/install.php https://www.macports.org/install.php
- KerrAvon 3y agoI remember this being a huge issue with MacPorts. It would never keep up with the damn releases, so if you were working on a beta OS, you were hosed until they caught up.
- halostatue 3y agoIt is, but it is mostly an issue with not having enough resources for the prebuilt images. They haven’t released a package installer for Sonoma yet, but AIUI the minimal required fixes have been in the MacPorts core for several weeks. There are likely to be more issues related to Apple's switch to the `prime` linker. (I’m a port contributor and am on macports-users where this issue has come up twice. There is what I think is excessive concern about the macOS beta NDA preventing the creation of a package installer until after GA when it no longer applies. A bigger problem is the availability of sufficient build hardware as they have a smallish Mac mini multi-booting into 11, 12, and 13.)
- saagarjha 3y agoI've been using MacPorts on beta releases for the last several years, and it does a pretty decent job. I wouldn't say it's significantly behind the competition.
- wwalexander 3y agoYou can just build the latest tarball from source with `./configure && make && make install` [1]. I did so just now without any issues. (You’ll need to install Xcode and the Developer Tools first if you don’t have them already.) [1] https://www.macports.org/install.php#source https://www.macports.org/install.php#source
- wwalexander 3y agoSorry, that should be ./configure && make && sudo make install
- joeman1000 3y agoLooks like it’s out now.
- n8henrie 3y agohttps://nixos.org/download.html#nix-install-macos https://nixos.org/download.html#nix-install-macos The homebrew team seems incredibly burnt-out, to the point of hostility. I've really enjoyed the nixpkgs community so far and encourage others to check it out; it hasn't replaced homebrew entirely for me (yet), but it's getting closer every day.
- oxonia 3y agoYes, the Homebrew message does seem unnecessarily hostile. Not everyone can afford to buy a brand new computer every year.
- Condition1952 3y agoThose peasants are bound to suffer the wrath of planned obsolescence. macOS could be a modular rolling release, but you need to milk the peasants from time to time
- dgacmu 3y agoThis seems a little exaggerated? Macos 12 will run on most Macs from 2015 and later. 8 year old hardware isn't Earth shattering, but it's also not a "hostile" period of time for a non-commercial open source project to support. And it's certainly not "new hardware every year".
- WillPostForFood 3y agoThe "period of time" isn't what was hostile.
- Uehreka 3y agoEdit: nevermind
- musicale 3y agoI wish there were a macOS (and Homebrew) "extended support" edition with security patches for 10 years rather than 7. Old Macs are often perfectly usable in terms of hardware, but macOS security updates have left them behind. As of today, it's likely that the 2016 Mac I'm writing this on (which can run Monterey but not Ventura or Sonoma) is out of support. Of course the Mac apocalypse will be when x86 support is dropped, possibly starting in the next macOS release.
- krackers 3y agoThese warnings keep getting longer every homebrew release. You may want to try macPorts, which goes out of their way to explicitly support releases all the way down to 10.5.
- cglong 3y agoWow! That's quite impressive. Meanwhile there was a latent bug in the Homebrew formula for Rust that affected 10.13 for a year until I finally spent a few hours to investigate it.
- musicale 3y agoOr pkgsrc from source (I think updated binary support is for Big Sur and newer.)
- koito17 3y agoOne of the cooler experiences I've had with MacPorts was seeing some people go out of their way to ensure builds still worked on PPC Tiger and PPC Leopard. I remember seeing SBCL builds broken on Darwin/ppc for a long while, and eventually SBCL decided to drop support for Darwin/ppc altogether. Still, these ports maintainers did not give up and eventually found a way to fix SBCL builds on PPC: https://trac.macports.org/ticket/65484 https://trac.macports.org/ticket/65484 I recall seeing some work to bring back PPC support upstream, but I am not sure what the progress on that is. It's still cool seeing downstream users fix builds that simply didn't work (and to the point where upstream decides to remove support entirely since they couldn't build it anyway).
- nortonham 3y agomacports is great! doesn't get enough love imo. same could be said for pkgsrc I guess. I've used that on other *nix systems; haven't tried it on MacOS yet but the fact it's an option is huge
- cellularmitosis 3y agoIndeed! I’ve also dabbled in this area http://leopard.sh/ http://leopard.sh/
- catlover76 3y ago"If you see a Homebrew maintainer walking down the street in your direction, find the nearest wall and bury your face in it in shame and deference until they pass."
- stalfosknight 3y agoThis is exactly the kind of vibe they give off on their Github repo too. They're not the nicest people to interact with.
- pkulak 3y agoWell, they have to spend their time propping up an OS built by one of the richest companies in the world for free.
- josephg 3y agoThey have chosen to. It’s a big difference!
- pkulak 3y agoChoices can make you unhappy.
- sph 3y agoIt appears that Sisyphus is unhappy, unless you are telling me they are free to move on, and being a Homebrew maintainer is not an eternal punishment?
- Klonoar 3y agoI mean, I’m sympathetic to OSS being hell but you don’t get this vibe from MacPorts. The tone with which they write that stuff actually makes me not use it - not because it’s not good (it generally is), I just get annoyed reading it.
- toyg 3y ago
- astrange 3y agoOnce again a good time to remember that there were multiple perfectly good package managers available when Homebrew was invented, they were more future-proof (by eg not putting files in /usr/local), and everyone only switched to it because for some reason Ruby programmers wanted all of their tools to be written in Ruby (and possibly by people with waxed mustaches.)
- headwayoldest 3y agoUltimately users will go where the package maintainers are. There are more people out there willing and able to write Ruby today than Perl (Fink) or TCL (MacPorts). I'm sure someone will start a macOS package manager based on python and yum to signal the waning days of those technologies.
- jcelerier 3y agoI'm secretly hoping for a makepkg / pacman-based replacement to homebrew, to have the same set of commands and package naming conventions across mac / win / linux
- astrange 3y agoWasn't there one? I know there is Nix for macOS, though it's probably not very maintained.
- wiml 3y agoThe Darwin nixpkgs is actually pretty active and healthy, in my experience.
- pxc 3y agoThere was one, and you can find it here: https://github.com/orgs/archmac/repositories https://github.com/orgs/archmac/repositories But it is unmaintained (it seems its author has moved on to Nix).
- wwalexander 3y ago
- runjake 3y agoContext? Homebrew is working fine on Sonoma here. I do not get that or a similar message.
- saaspirant 3y agoHe is talking about MAC OS 11 Big Sur
- georgespencer 3y agomacOS or MacOS but never MAC OS or MACOS. MAC is an acronym for Media Access Control (as in: MAC address), Mac (or mac) is an abbreviation of Macintosh.
- deleted 3y ago[deleted]
- SwiftyBug 3y agoMAC is also a cosmetics company (https://www.maccosmetics.com/ https://www.maccosmetics.com/). It can be many things.
- georgespencer 3y agoAnother good reason to properly style things.
- deleted 3y ago[deleted]
- bastardoperator 3y agoApparently hating on homebrew is super popular right now. I run brew on osx and linux and have zero issues.
- sph 3y agoNo one is talking about issues here.
- climb_stealth 3y agoOh oh, it's getting closer. Currently on MacOS 12 with my trusted 2015 Macbook Pro. It still goes strong, but looks like the next major release may see the end of homebrew for this one. There's really no issue with this computer other than 16gb of RAM being a bit tight when every modern app is using Electron. Oh well, see how we go.
- cauthon 3y agoFedora mostly works out of the box on my 2015 MBP
- famicom0 3y agoHow’s resolution scaling? I tried Fedora KDE and setting a scaled resolution didn’t do anything.
- raunakchhatwal 3y ago[dead]
- Fnoord 3y ago(Message also for your parent) Last week, I saw the writing on the wall. I installed OpenCore-Legacy-Patcher on two MBPs from 2015, updating 12.7 to 13.6. It is a MBP 13" 2015 (early 2016 variant) and a MBP 15" 2015 (late 2015?). Works very well but you need to follow the guide. Both machines are still working well, 'cept for the battery (already replaced on the 13"). Esp the 15" is still in good condition, my wife happily uses it and insists on needing a 15". So a replacement would be expensive. [1] https://dortania.github.io/OpenCore-Legacy-Patcher/INSTALLER.html https://dortania.github.io/OpenCore-Legacy-Patcher/INSTALLER...
- ewoodrich 3y agoCan confirm Ventura runs great on a mid-2015 MacBook Pro 15 inch (MacBookPro11,4). Mine has 16gb of RAM and an i7 which probably helps (also added a modern 1tb NVMe drive via an adapter). I use it for a dedicated music production setup and only ever hear fans when installing something or during updates. My only advice for someone new to OCLP/unfamiliar with Mac boot loader in general (like me one week ago) is that the OCLP boot screen during setup looks very similar to the native MacOS boot picker and went through four different flash drives trying to follow the instructions thinking it wasn't booting properly from the drive. Look closely at the instruction screenshot to distinguish them.
- jonhohle 3y agoCome over to MacPorts. It’s friendlier over here and stuff is supported and no one uses words like formulae.
- WesolyKubeczek 3y agoThey use Tcl, though, but I guess there is always bound to be an abomination in every project…
- Klonoar 3y agoThis is my only true gripe with MacPorts. Tcl made some sense ~20 years ago but it’s 2023 and the only time I ever touch it anymore is for MacPorts itself.
- saagarjha 3y agoAmusingly it makes a lot of sense today, by accident: Tcl happens to be one of the only scripting runtimes left on a base macOS install.
- WesolyKubeczek 3y agoThere are two versions of Perl, awk, and Ruby in a fresh Sonoma install. I would say that moving Python away into XCode tools was an easy thing to do, but to rip the others away, it will take quite an effort. I predict that Apple will admit defeat at the very least with Perl, one of the biggest beneficiaries of the Lindy effect. It has entrenched itself so much that you won't just yank it away without some serious bleeding. Also, there is jsc if JavaScript is what floats your boat, although it's buried quite deep.
- cpeterso 3y agoI'm surprise Apple doesn't, even unofficially, upstream fixes to Homebrew before a new macOS version is released. Why let Homebrew break for so many macOS users on day 0? I know Apple is secretive about unreleased products, but the type of fixes for Homebrew wouldn't reveal too many Apple secrets. Do Apple engineers not use Homebrew on their own Macs while developing macOS?
- chii 3y ago> Why let Homebrew break for so many macOS users on day 0? why pay for work when it would've been done for free and apple gets to reap the financial benefits?
- walteweiss 3y agoI see other replies as well, but I just want to tell you guys I came here to recommend mac ports. It’s a shame brew is so popular and mac ports having only a fraction of that attention.
- tacker2000 3y agoYea the homebrew dev team is pretty user hostile tbh. The more you read their github, the more you realize how insufferable and arrogant they are. It leaves a very bad impression. Also, if you are not going along in the upgrade rabbit race, homebrew gets really annoying and actually in your way at some point. I see myself moving to macports soon, if brew gets worse and the stability of my setup is compromised (lots of php versions with valet for example). I guess brew is now more targeted at “prosumers” now since it is imposing unnecessary limits on what “pro” users want and need.
- andy_ppp 3y agoI always expect endless support from free products, built by the community, that I'm not paying for or contributing to.
- tacker2000 3y agoOf course the devs dont need to support everyone and answer every feature request. Its more nuanced than that. As a dev, i like a stable environment and i dont like to do big updates all the time, since that means i have to spend hours updating my setup again. Everytime i run brew im scared it will hose my PHP versions, etc, since it auto updates everything. To install old PHP versions one needs to hack the install files to make it work. If you bring up any of these issues you are screamed down by the devs as “you should always be on the latest versions anyway bla bla”… but that is just not a realistic scenario in the real world. Legacy code is everywhere. In the end brew is not really for pro users, but, as i said, maybe for people using it to install youtube-dl or whatever. Once the pain of reinstalling and hacking it to make it work becomes too big then i will switch.
- kalleboo 3y agoI'm glad we have both Homebrew as well as MacPorts. It's like having options to choose a bleeding-edge or stable distro. I prefer the former (as a dev, who often wants to use reasonably new features and libraries - and honestly despite keeping up in versions I can count the breakage to my workflow in the past decade on one hand, at least I'm not a JavaScript developer) but I totally respect the latter as well, so I'm glad we can each have what we need.
- rswail 3y agoUse MacPorts instead. I run: $ sudo bash # port selfupdate && port -u -c upgrade outdated && port reclaim once a week. When I upgraded to Ventura (from Big Sur), I followed the instructions for an OS upgrade and everything moved across cleanly. It installs itself in /opt It works with MacOS's Frameworks for stuff like python and java. It allows you to run multiple versions with "port select". Why would I want to run anything else?
- tempodox 3y agoSince I've changed to MacPorts many years ago, I never had any such trouble.
- FridgeSeal 3y agoOut of date OS doesn’t receive support. I for one, am shocked. Maintainers of popular free, open source community tool are tired of being asked to support out of date OS. Colour me even more surprised!
- jt2190 3y agoI assume that the message means that Homebrew is incorrectly identifying the installation of MacOS Sonoma as “out of date”, and that means updating Hombbrew is a side-effect of updating the OS.
- Cub3 3y agoYou get what you pay for
- racl101 3y agoOof. I think I gotta switch to Linux. I already loathe brew.
- smrtinsert 3y agoMy blood pressure is rising just reading this...