-
Notifications
You must be signed in to change notification settings - Fork 359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to upgrade to mamba 2.0 #3503
Comments
Thank you for reporting the problem and showing your appreciation, @zaneselvans. A reproducer would better help us understand and solve the problem. Do you have a specification of the environment we could use to reproduce it? |
This was in the To reproduce: curl -L -O "https://github.com/conda-forge/miniforge/releases/latest/download/Miniforge3-$(uname)-$(uname -m).sh"
bash Miniforge3-$(uname)-$(uname -m).sh
mamba activate base
mamba install "mamba==2.0.2" Installed packages (from
After running
And it's still unable to solve if I try to install
|
The update will be possible once |
One should be able to perform the update if you uninstall For instance:
|
Ah okay. That makes sense. I'll keep an eye on that issue. Thanks! |
You can also downgrade |
After using micrmamba to remove conda and update mamba, I can install packages with mamba but can't activate environments with mamba because I think it is pointing to conda in my .zshrc
my .zshrc
|
Hi @rbavery, I would recommend adapting your path so that
|
@jaimergp published This can help updating to mamba 2.0 for installations depending on
|
As mentioned by @jaimergp,
|
Troubleshooting docs
Anaconda default channels
How did you install Mamba?
Mambaforge or latest Miniforge
Search tried in issue tracker
2.0 upgrade and also SOLVER_RULE_UPDATE
Latest version of Mamba
Tried in Conda?
Not applicable
Describe your issue
Maybe this isn't supposed to work yet, but it seems to be impossible for me to upgrade to mamba 2.x using Miniforge since mamba depends on conda, and conda depends on libmambapy which isn't compatible with the new solver library.
In my
base
environment, after a fresh re-install using them most recent Miniforge I attempt to install the most recent version ofmamba
that's available: v2.0.2 and get a solve failure.I imagine there's a way to tell it explicitly to switch to using the new C++ only solver instead of the python wrapper, but I haven't found when looking at the Troubleshooting page, or the What's Different in Mamba 2.0 page or the rest of the docs. The message about the
SOLVER_RULE_UPDATE
seemed relevant, but I didn't find any issues that seemed to be related to this.Thank you for all your hard work on this. I'm glad you've had a chance to clean up the underlying mamba code, and I'm excited for the update.
mamba info / micromamba info
Logs
environment.yml
No response
~/.condarc
The text was updated successfully, but these errors were encountered: