no way to install on Mac Os

Deprecated Sequoia Beta Bug Reports
1

I have tried with all the installers for Mac Os, but none works on my MAc…
Model Name: MacBook Pro
Model Identifier: MacBookPro10,1
Processor Name: Intel Core i7
Processor Speed: 2.7 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Memory: 16 GB
Boot ROM Version: MBP101.00EE.B02
SMC Version (system): 2.3f36
Serial Number (system): C02JQ3R7DKQ5
Hardware UUID: 197A8F8C-9E82-5B6A-932D-F05D17607A07

2

Hi. We’d like to take a look at what’s being printed out on the terminal. Can you try running Sequoia through it?

  1. Browse over to where you have Sequoia installed. Right click on the application and select “Show Package Contents”. Browse to “Contents” -> “MacOS”. There should be a single executable called “Sequoia” in there.
  2. In the dock, open up Terminal (if it’s not there, Open Finder, click on “Applications” in the “Favorites” section, and go to the “Utilities” folder. The Terminal executable should be there).
  3. Drag the executable you found in step 1 and drop it on the Terminal. It will fill in with something like "/[Wherever you placed Sequoia]/Sequoia-0.0.16.57940-osx/Sequoia.app/Contents/MacOS/Sequoia
  4. In the Terminal press “Enter”. Sequoia will start up as normal.
  5. After Sequoia quits, can you copy and paste any messages that have been printed out here? You should be able to just click and drag to highlight each line in the Terminal, right click, and then select “Copy”
3

ok, this is the terminal:
Last login: Tue Mar 10 10:31:53 on console
TTS-120496ML:~ xmartin61$ /Users/xmartin61/Downloads/Sequoia-0.0.15.57858/Sequoia.app/Contents/MacOS/Sequoia ; exit;
libc++abi.dylib: terminating with uncaught exception of type boost::exception_detail::clone_impl<boost::exception_detail::error_info_injectorboost::system::system_error >: resolve: Host not found (authoritative)
Abort trap: 6
logout

[Process completed]

4

it doesn’t start even from the terminal…

5

Hi. I think we’ve managed to fix the bug. The next build should work so once that’s available let us know if you still run into any issues.