-
Notifications
You must be signed in to change notification settings - Fork 24
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
installing libzlib in base results in libmamba updates #240
Comments
This is because you are adding Instead, with
, which is closer to what you'd expect. That said, I do agree that the behaviour is totally different, and I can't observe this in micromamba, so we'll take a look and see if we can tame it down a bit ;) |
Regardless of the channel order, I don't understand why I am getting updates when I didn't ask for updates. I just was installing one package. Why should changing the order implicitly enable updates? |
Checklist
What happened?
In a docker based CI job, we start out by setting up the libmamba solver and installing some other tools.
We were surprised to find out that libmamba was getting upgraded despite the fact that we did not install
any packages that depend on libmamba directly or indirectly. This ONLY happens if libmamba is configured
as the current solver.
This adds significant extra cost to the install. In the example below, using libmamba results in a build time of 2 minutes and 40 seconds vs. just 40 seconds using libmamba, and the extra time does seem directly related to upgrading libmamba.
On top of the extra time, the other concern is that this essentially forces you to use the latest version of libmamba whether you want to or not.
I also find this behavior surprising since it appears that libmamba already indirectly depends on libzlib
One minimal example is to just install libzlib, although any package that depends on libzlib indirectly will also trigger this behavior.
These are all based on the continumio:miniconda3 docker image.
This is what it looks like without libmamba enabled:
If you do this wi
Conda Info
No response
Conda Config
No response
Conda list
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: