You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My problem is not solved in the Troubleshooting docs
Anaconda default channels
I do NOT use the Anaconda default channels (pkgs/* etc.)
How did you install Mamba?
Mambaforge or latest Miniforge
Search tried in issue tracker
yes
Latest version of Mamba
My problem is not solved with the latest version
Tried in Conda?
I have this problem with Conda as well, without using Mamba
Describe your issue
We have been using the simple command:
mamba env create || mamba env update
to ensure that an environment (a) exist and (b) is up-to-date. This no longer appears to work with mamba 2.0, and I can't find a simple substitute for it. If I use mamba create -n <env name>, I'll get an interactive prompt if the environment already exists. If I add -y, then it will empty out the environment. Also, mamba env update now seems to require explicitly passing an -f environment.yml file argument.
This is definitely more complicated and it requires another non-mamba command. I'd welcome a better suggestion on how to write this, but I also suspect that adding a -n option to mamba (or some way to fail quickly) would be a good thing. Also of note is that mamba env create also now requires a -f environment.yml and will again clobber the entire environment if we pass it the -y argument (whereas I'd like this command to just update missing dependencies). Thanks for your help.
mamba info / micromamba info
No response
Logs
No response
environment.yml
No response
~/.condarc
No response
The text was updated successfully, but these errors were encountered:
Troubleshooting docs
Anaconda default channels
How did you install Mamba?
Mambaforge or latest Miniforge
Search tried in issue tracker
yes
Latest version of Mamba
Tried in Conda?
I have this problem with Conda as well, without using Mamba
Describe your issue
We have been using the simple command:
to ensure that an environment (a) exist and (b) is up-to-date. This no longer appears to work with mamba 2.0, and I can't find a simple substitute for it. If I use
mamba create -n <env name>
, I'll get an interactive prompt if the environment already exists. If I add-y
, then it will empty out the environment. Also,mamba env update
now seems to require explicitly passing an-f environment.yml
file argument.The best I could come up with is:
This is definitely more complicated and it requires another non-mamba command. I'd welcome a better suggestion on how to write this, but I also suspect that adding a
-n
option to mamba (or some way to fail quickly) would be a good thing. Also of note is thatmamba env create
also now requires a-f environment.yml
and will again clobber the entire environment if we pass it the-y
argument (whereas I'd like this command to just update missing dependencies). Thanks for your help.mamba info / micromamba info
No response
Logs
No response
environment.yml
No response
~/.condarc
No response
The text was updated successfully, but these errors were encountered: