![]() ![]() At this point I was able to install mamba but for some reason, only version 0.7.6 (running mamba update mamba reported nothing to be done). Then, immediately after installation, I added the conda-forge channel and removed the defaults. (for some reason I had to manually specify to install mamba=0.24, the latest, or it was stuck at 0.7.)ĮDIT2: another workaround I found is to install the latest anaconda. At that point, mamba is able to perform more or less all install and update operations. One workaround I found thus far is to install a previous version of anaconda (Nov 2021), then before doing anything else (so before updating), I add conda-forge and install mamba. ![]() I install the latest anaconda, then I add conda-forge channel and make priority strict, and nothing works anymore. add conda-forge channel (or use it to install anything)ĮDIT: I could observe this also in another machine, that did not have conda installed before (XFCE Manjaro in a VirtualBox VM).In my case I was able to reproduce this from a fresh new anaconda installation (see here). (Everything as always worked fine for me until a few days ago) Is it something broken with conda-forge and the latest anaconda? I'm not able to install anything whenever I either add that channel or simply specify it as install option. It seems the issue comes from conda-forge channel. Package cache : /glade/scratch/chayan/.conda/pkgsĮnvs directories : /glade/u/apps/opt/conda/envs Populated config files : /glade/u/apps/opt/conda/.condarcīase environment : /glade/u/apps/opt/conda (read only)Ĭonda av data dir : /glade/u/apps/opt/conda/etc/conda User config file : /glade/u/home/chayan/.condarc Active environment : /glade/work/chayan/miniconda3/envs/geo_scipyĪctive env location : /glade/work/chayan/miniconda3/envs/geo_scipy
0 Comments
Leave a Reply. |