macos: Auto update installs wrong architecture
See original GitHub issueJust an FYI, every time an update occurs with Tabby on M1 mac I’m finding that it installs the x86_64
package instead of arm64
This consequently means that it runs terminals in an ‘emulated’ type of mode and causes odd behaviour or errors in things that are specifically expecting the correct architecture, such as brew:
Error: Cannot install under Rosetta 2 in ARM default prefix (/opt/homebrew)!
To rerun under ARM use:
arch -arm64 brew install ...
To install under x86_64, install Homebrew into /usr/local.
Reinstalled every update to the arm64 package so far resolves this.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
If an error occurred while updating or installing macOS
If an error occurred while updating or installing macOS · Check your internet connection · Install in safe mode · Install after repairing...
Read more >Do automatic macOS updates work for you? They don't for me
I get the notification and it downloads all the files. But, restarting macOS does not automatically update it. I have to go into...
Read more >Error: Cannot install in Homebrew on ARM processor in Intel ...
One idea is that Xcode Command Line Tools aren't installed. xcode-select -p to check if installed; xcode-select --install to install. Another ...
Read more >Cant't open on my MacOSX 10.5.8 PPC wrong architecture ...
MacOS says something about wrong architecture and the Firefox icon shows a diagonal line across the icon to drag into the application.
Read more >brew(1) – The Missing Package Manager for macOS (or Linux)
cask: Homebrew package definition that installs macOS native applications ... --auto-update : Run on auto-updates (e.g. before brew install ).
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The latest release now uses Keygen and separate update channels per arch, so this won’t come up again with the next update.
Good to hear! I still have no idea what could have gone wrong with .186 unfortunately as x64 and arm64 builds are now completely different “products” in the auto-updater service