Dependency hell installing mamba

Users mamba
1

conda install -n base -c conda-forge mamba

3 hours and still running:

Retrieving notices: …working… done
Collecting package metadata (current_repodata.json): done
Solving environment: unsuccessful initial attempt using frozen solve. Retrying with flexible solve.
Solving environment: unsuccessful attempt using repodata from current_repodata.json, retrying with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: unsuccessful initial attempt using frozen solve. Retrying with flexible solve.
Solving environment: \

The irony is that I’m installing mamba to get away from the klunky and slow conda. Is this a feature or a bug?

1 Like
2

@noguano,

If I was in your shoes, I would follow the installation instructions for Miniforge (GitHub - conda-forge/miniforge: A conda-forge distribution.) and install it alongside your existing conda installation. By doing this, you’ll still be able to use all of the existing conda environments in your old installation, and you will have a new installation with mamba.

3

Also, the Miniforge installer is officially recommended by the Mamba project: Mamba Installation — documentation