Closed abourrier closed 1 year ago
cc @conda-forge/constructor
I can confirm that this is indeed a bug
It might be that we are hitting this bug https://github.com/mamba-org/mamba/issues/2187
I'm somewhat surprised that this issue didn't occur earlier since the last time we updated micromamba was a few months back https://github.com/conda-forge/miniforge/pull/383
It is due to a bug in micromamba: https://github.com/mamba-org/mamba/issues/2187
I think we could accelerate the release of https://github.com/mamba-org/mamba/pull/2265
but the same people that would review a patch proposed for the conda-forge only version would review a patch for the upstream repository.
I can apply the patch to conda-forge once they accept it there.
Does it reproduce with CONDA_OFFLINE=true
set?
Given the code path I've identified it is going through, i'm willing to bet it is still an issue.
Solution to issue cannot be found in the documentation.
Issue
OS: Ubuntu 20.04
When trying to install Mambaforge 22.11 on a platform not connected to the Internet, the installer tries to update some packages right away and I get the following error:
Previous versions of Mambaforge up to 22.09 did not have this problem.
Installed packages
Environment info