mamba install with libarchive.13.dylib on M2 Mac about biostar-handbook HOT 4 OPEN

This is an issue that I hope to get to the bottom of this Fall, when I'll have the software installed on dozens of computers at the same time. It is hard to troubleshoot because the installation on my M2 it worked just fine with no problems. And then it is difficult to undo the install to try fresh with different parameters.

I believe one needs to run the Intel-based conda installer even on M1. It should run seamlessly under emulation.

And when that happens the whole system runs in Intel emulation mode and it will run and install the Intel-based software all run under emulation. I have a new M1 and ran the install with no problems.

But when someone installs the native M1 conda install then they can run into trouble.

What I have not 100% figured out yet is why sometimes the Intel based installer does not want to work on M1.

from biostar-handbook.

Ah, good to know. This is a brand new laptop with no other software installs. I deleted miniconda3 several times in the aims of getting this to work so maybe I inadvertently fixed something else along the way

from biostar-handbook.

I think the biggest issue is something with the libarchive and mamba dependencies. Here's a thread on it: mamba-org/mamba#1826

from biostar-handbook.

The installation instructions have been rewritten to use micro mamba a simplified and more general version of mamba

https://mamba.readthedocs.io/en/latest/micromamba-installation.html

from biostar-handbook.