jaimergp
commented
10 hours ago Hm, conda-libmamba-solver should have been repodata-patched to prevent this. Let me check if 23.11 also received the patch 🤔
Open CsatiZoltan opened 14 hours ago
jaimergp
commented
10 hours ago Hm, conda-libmamba-solver should have been repodata-patched to prevent this. Let me check if 23.11 also received the patch 🤔
jaimergp
commented
10 hours ago Yes, all repodata looks correct 🤔
$ conda repoquery search conda-libmamba-solver --json --platform linux-64 | grep libmambapy
"libmambapy >=1.5.6,<2.0a0",
"libmambapy >=1.5.6,<2.0a0"
"libmambapy >=1.5.6,<2.0a0"
"libmambapy >=1.5.6,<2.0a0"
"libmambapy >=1.5.3,<2.0.0a0"
"libmambapy >=1.5.3,<2.0.0a0"
"libmambapy >=1.5.3,<2.0.0a0"
"libmambapy >=1.5.1,<2.0.0a0"
"libmambapy >=1.5.1,<2.0.0a0"
"libmambapy >=1.5.1,<2.0.0a0"
"libmambapy >=1.5.1,<2.0.0a0"
"libmambapy >=1.4.1,<2.0.0a0",
"libmambapy >=1.4.1,<2.0.0a0",
"libmambapy >=1.4.1,<2.0.0a0",
"libmambapy >=1.0.0,<2.0.0a0",
"libmambapy >=1.0.0,<2.0.0a0",
"libmambapy >=0.23,<2.0a0"
"libmambapy >=0.23,<2.0a0"
"libmambapy 0.22.*"
"libmambapy 0.22.*"What's the output of which mamba? After updating to v2 you shouldn't be hitting the conda code paths, because v2 is pure C++ 🤔
CsatiZoltan
commented
10 hours ago It's in the base environment: /home/zozo/mambaforge/bin/mamba.
jaimergp
commented
10 hours ago Is that a binary executable or a Python script?
CsatiZoltan
commented
10 hours ago A binary executable.
jaimergp
commented
9 hours ago The only thing I can think it's happening is that the environment is getting "reactivated" after the install, which somehow runs conda code. If you are using mamba primarily, you can ignore the conda-libmamba-solver warning. At some point we will release a version compatible with libmamba v2 too (before the year ends). If it gets reeeally annoying, I think you can set CONDA_NO_PLUGINS=1 or CONDA_SOLVER=classic and maybe that way the warning disappears? Let me know if that helped.
CsatiZoltan
commented
9 hours ago the environment is getting "reactivated" after the install
Probably true: when I open a new terminal, I get the same message. This is the time when the base environment is sourced.
If you are using
mambaprimarily, you can ignore theconda-libmamba-solverwarning.
Yes, I use mamba. For curiosity, I ran the same command (update a certain package) with conda instead of mamba. The error/warning is the same, but this time it wants to install and update a lot of packages (which I refused). Given that both conda and mamba use the same channel (conda-forge), there must be a difference in the dependency solving. Could you point me to a resource why the dependency solving differs in mamba wrt conda? I thought that mamba is a faster and drop-in replacement for conda.
I think you can set
CONDA_NO_PLUGINS=1orCONDA_SOLVER=classicand maybe that way the warning disappears?
Exporting these variables in the same terminal before using the mamba/conda commands did not help in suppressing the message.
At some point we will release a version compatible with libmamba v2 too
OK, I can live with it, it is not too annoying. I propose that we keep this issue open until then.
jaimergp
commented
9 hours ago Could you point me to a resource why the dependency solving differs in mamba wrt conda?
This is a good start: https://conda.github.io/conda-libmamba-solver/user-guide/libmamba-vs-classic/ Then https://mamba.readthedocs.io/en/latest/advanced_usage/package_resolution.html.
Probably true: when I open a new terminal, I get the same message. This is the time when the base environment is sourced.
You might be able to get rid of the conda initialize block, and then run mamba init to populate the activation logic with only mamba instead. Maybe that works!
CsatiZoltan
commented
9 hours ago Thanks for the links.
How should I use mamba init? It is not apparent for me from the help menus.
Checklist
What happened?
After updating mamba to from 1.5.9 to 2.0.2 (which automatically updated the dependencies libmamba and libmambapy, in addition to fmt from 10.2.1 to 11.0.2), the
mamba updatecommands display the error in the title of this issue. I can install packages, but after the "Transaction finished" message, the additional error message is displayed. I use mambaforge.Conda Info
Conda Config
Conda list
Additional Context
No response