Upgrading Homebrew and avoiding the "failed to verify attestation" error
til.simonwillison.net
Upgrading Homebrew and avoiding the "failed to verify attestation" error
1–10 of 46 posts
Re: Upgrading Homebrew and avoiding the "failed to verify attestation" error
#2I’ve switched over to devbox, which is a thin, easy to use wrapper around Nix on osx. Haven’t had to install brew yet. Brew was simple in theory but I always ran into so many issues like this, or just various packages polluting everything. Fingers crossed I don’t have to go back
As someone who hates tinkering with this kinda stuff, I’m surprised how well it works so far
Re: Upgrading Homebrew and avoiding the "failed to verify attestation" error
#3I’ve switched over to devbox, which is a thin, easy to use wrapper around Nix on osx. Haven’t had to install brew yet. Brew was simple in theory but I always ran into so many issues like this, or just various packages polluting everything. Fingers crossed I don’t have to go back As someone who hates tinkering with this kinda stuff, I’m surprised how well it works so far
MacPorts is a great alternative, also way older but never has been as successful as Homebrew.
Re: Upgrading Homebrew and avoiding the "failed to verify attestation" error
#4I’ve switched over to devbox, which is a thin, easy to use wrapper around Nix on osx. Haven’t had to install brew yet. Brew was simple in theory but I always ran into so many issues like this, or just various packages polluting everything. Fingers crossed I don’t have to go back As someone who hates tinkering with this kinda stuff, I’m surprised how well it works so far
MacPorts is a great alternative, also way older but never has been as successful as Homebrew.
Second recommendation for MacPorts
It predates Homebrew by a bit and is under Apple's http://www.macosforge.org umbrella of OSS projects, so as close to 1st party support as you can get.
Re: Upgrading Homebrew and avoiding the "failed to verify attestation" error
#5> I frequently have rate limiting problems with my GitHub account
What are people doing to get their account rate limited?
Re: Upgrading Homebrew and avoiding the "failed to verify attestation" error
#6> I frequently have rate limiting problems with my GitHub account What are people doing to get their account rate limited?
[deleted]
Re: Upgrading Homebrew and avoiding the "failed to verify attestation" error
#7I’ve switched over to devbox, which is a thin, easy to use wrapper around Nix on osx. Haven’t had to install brew yet. Brew was simple in theory but I always ran into so many issues like this, or just various packages polluting everything. Fingers crossed I don’t have to go back As someone who hates tinkering with this kinda stuff, I’m surprised how well it works so far
My issues with homebrew are:
1. I hate the concept of dependency management. I want every package to ship with all dependencies inside. Just download tarball, extract and that's about it.
2. homebrew often wants to install things I already have, like python.
3. No easy way to install old packages.
I don't understand why things are made harder than they should be.
Re: Upgrading Homebrew and avoiding the "failed to verify attestation" error
#8All I can say when I see Homebrew: "I replaced Homebrew with Devbox" [1]
[1] https://mootoday.com/blog/i-replaced-homebrew-with-devbox
Re: Upgrading Homebrew and avoiding the "failed to verify attestation" error
#9> I frequently have rate limiting problems with my GitHub account What are people doing to get their account rate limited?
CI/CD pipelines at large scale can pull directly from src repos sometimes causing stuff like this, just off the top of my head. I think the default is 5000 per hour which is not very much for automation to chew through. I ran into something similar with bitbucket once that I had to engineer around because it was very annoying.
Re: Upgrading Homebrew and avoiding the "failed to verify attestation" error
#10I’ve switched over to devbox, which is a thin, easy to use wrapper around Nix on osx. Haven’t had to install brew yet. Brew was simple in theory but I always ran into so many issues like this, or just various packages polluting everything. Fingers crossed I don’t have to go back As someone who hates tinkering with this kinda stuff, I’m surprised how well it works so far
My issues with homebrew are: 1. I hate the concept of dependency management. I want every package to ship with all dependencies inside. Just download tarball, extract and that's about it. 2. homebrew often wants to install things I already have, like python. 3. No easy way to install old packages. I don't understand why things are made harder than they should be.
Dependencies are totally out of control, in much of OSS, not just Homebrew. I probably have 5-6 leaf node packages that I actually installed with brew install, but brew list shows close to 100 little dependencies. Same with apt on my Ubuntu/Debian systems. I physically installed a handful of applications but my system has hundreds of packages installed. At least it’s not DLL Hell: the dependency management tools are great and uninstallation is clean, but wow what an explosion of quantity of dependencies!
I don’t use node but I understand it’s a mess there too.