Homebrew M1 conda update -n base conda: The environment is inconsistent, please check the package plan carefully
#325
Comments
|
I consider the:
as no harm, so I have accepted the update. But still want to make a second check here. |
|
same problem here on my m1 mba. |
|
Having the same issue unfortunately. Completely clean install on Mambaforge (both arm64 and i386 on M1): Jupyter is also broken... |
|
Same problem here! |
|
Sorry for the delay. Ultimately, we aren't always able to recreate in every downstream packaged environment. Can any of you recreate without homebrew? If not. You might get better help asking the homebrew devs directly :/ |
|
@hmaarrfk I don't think it's a homebrew issue, I used the installer https://github.com/conda-forge/miniforge/releases/latest/download/Mambaforge-MacOSX-arm64.sh As a workaround, I switched from Mambaforge to Miniconda cd `mktemp -d`
wget https://repo.anaconda.com/miniconda/Miniconda3-latest-MacOSX-arm64.sh
bash Miniconda3-latest-MacOSX-arm64.sh -b -p "$__conda_prefix"
echo "channels: [conda-forge]" > "$__conda_prefix/.condarc"
$__conda_prefix/bin/conda update -y --all
$__conda_prefix/bin/conda install -y mambaThis seems to work. |
|
Thank you for pointing me to that detail. It is, indeed odd. |
|
Looks like it is fixed now. Updated all environments. |
I doubt it! I still get the same errors! |
I still got the same issue. |
|
There's a potential 1-line fix if using homebrew-installed I seemingly was just able to fix this on a 2022 M1 MBP where I encountered this from a completely clean homebrew-installed That updated |
✔ ~ % conda update -n base conda 16:16:24
Collecting package metadata (current_repodata.json): done
Solving environment: done
# All requested packages already installed.it seems that the problem is resolved now. |
still got the errors sheng@liu ~ % conda update -n base conda > 1.txt The environment is inconsistent, please check the package plan carefully
==> WARNING: A newer version of conda exists. <== Please update conda by running |
|
Brand new M1 MBP with freshly installed Miniforge and am getting the same errors. Has a solution been found (either with AND without home-brew)? The environment is inconsistent, please check the package plan carefully
==> WARNING: A newer version of conda exists. <== Please update conda by running $ conda update -n base conda |
|
@ngam are you able to help here? I don't have a mac, but it seems like you might have some useful input. |
|
I will try to reproduce... |
|
I can reproduce. When was the last time we updated our mambaforge/miniforge package list? Here are my quick thoughts ---
Full history of the second point: TLDR
NOTE: |
|
@hmaarrfk I am not familiar how we decide to freeze a certain package list, but I am not sure why the default mambaforge is still stuck on an older conda/mamba combo. I think force-updating this (especially after the drama with mamba and conda breaking around the most recent updates) makes most sense. I am not too familiar with the logistics though, so idk if this idea makes any sense as a more sustainable solution. |
|
Thanks for chiming in. I think there was some hesitancy in updating mamba though I think it has largely gone away. Not sure why this PR has remained as a draft for so long. Hopefully next week we can move on it. |
|
Ah I see #301 now, though is it at all possible to just change the list of packages? I tested the artifacts produced by #301 here https://github.com/conda-forge/miniforge/actions/runs/2660176511 and they don't have this issue on osx-arm64. For a quick fix, could it be possible to just to rerun the actions without any changes (i.e. without bumping the version)? |
|
Fwiw, the latest PR's (pushed into main) artifacts in https://github.com/conda-forge/miniforge/actions/runs/2659924106 don't have this problem. So you could simply cut a release without even updating mamba version |
|
We released a new version on miniforge. Hopefully it will get to homebrew soon and alleviate these problems |
|
@hmaarrfk this issue is now resolved. I tested it locally. Feel free to close it |
|
Thank you all for your patience. Feel free to open an issue if this comes up again. I think significant changes happened that it makes the information here somewhat stale |
|
Hi, I installed miniforge a couple of weeks ago on and M1 and ran into the same issues described above. Error: Cask 'mambaforge' conflicts with 'miniforge'. Should I just try to reinstall everything? |
Solution to issue cannot be found in the documentation.
Issue
I have accepted the update by entering
yInstalled packages
Environment info
The text was updated successfully, but these errors were encountered: