Open corneliusroemer opened 2 years ago
isuruf
commented
2 years ago You can do a separate installation of mambaforge using
curl -L -O "https://github.com/conda-forge/miniforge/releases/latest/download/Mambaforge-$(uname)-$(uname -m).sh"
bash Mambaforge-$(uname)-$(uname -m).shand then use that conda/mamba to repair the old installation by doing
conda install libffi libsolv --force-reinstall -p /opt/homebrew/Caskroom/mambaforge/base/
corneliusroemer
commented
2 years ago Thanks @isuruf - that's helpful but it doesn't seem to work.
Something is confused about architectures and I have no clue to fix.
After doing a separate installation of mambaforge, I had to first figure out how to deactivate the base environment:
./mambaforge/bin/conda config --set auto_activate_base false
conda deactivateOtherwise the broken environment would still be active:
Looking for: ['libffi', 'libsolv']
pkgs/main/osx-64 4.5MB @ 3.2MB/s 1.5s
bioconda/noarch 3.7MB @ 2.4MB/s 1.7s
bioconda/osx-64 3.5MB @ 2.1MB/s 1.8s
pkgs/r/noarch 1.3MB @ 715.4kB/s 0.4s
pkgs/main/noarch 816.0kB @ 396.0kB/s 0.5s
pkgs/r/osx-64 820.9kB @ 392.9kB/s 0.4s
conda-forge/noarch 9.3MB @ 3.2MB/s 3.2s
conda-forge/osx-64 23.1MB @ 2.7MB/s 9.3s
error libmamba Selected channel specific (or force-reinstall) job, but package is not available from channel. Solve job will fail.
error libmamba Selected channel specific (or force-reinstall) job, but package is not available from channel. Solve job will fail.
Pinned packages:
- python 3.10.*It doesn't want to work so I'm installing miniforge now, hoping that conda remains as a fallback in case mamba breaks again.
Something's very broken about architecture resolution.
Solution to issue cannot be found in the documentation.
Issue
I used the ARM mambaforge to install mamba on my apple silicon M1.
My base environment is hence in arm.
But to use nextstrain, I have an x86 environment, configured more or less as follows:
I can't quite remember what exactly I did, but my thinking is that I updated
mambafrom the x86 directory, maybe throughupdate --all.In any case, I now can no longer run
mamba. So I can't even export packages to reinstallmambaforgeand get back to my latest state.I've described the issue originally in the mamba repo but was told that they couldn't do much.
Maybe this is more of a miniforge issue than a mamba issue: https://github.com/mamba-org/mamba/issues/1897#issue-1360106036
In any case, does anyone know what I can do to rescue myself?
Maybe fat binaries of the mamba libraries would make it possible to use mamba in both x86 emulation and arm environments?
Error: