-
Notifications
You must be signed in to change notification settings - Fork 358
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
Channel priority not maximized over competing goals #532
Comments
even with strict-channel-priority? That is (afaik) recommended for the conda-forge use-case. |
If So, are you saying |
@mbargull with a flexible channel priority, mamba will always choose the higher version, independent of the channel it came from. Although I just re-checked the docs on conda and it seems that indeed, I misinterpreted them before. There is a similar issue for our (too lax) strict channel priority: #559 |
@mbargull we've changed the default now to better match conda's behavior:
|
Sounds good, thanks Wolf, very much appreciated!
What does "only directly" mean in this context? |
let's say you have channel A (prio 10)
channel B (prio 0)
Now if you have flexible prio you can do Similarly if you |
Perfect, thanks again! |
mamba
seemingly prioritizes the package count minimization or package version maximization over channel priority.In the case below it is expected (at least with
conda
's semantics) thatconda-forge::libxcb
gets chosen, butmamba
choosesdefaults::libxcb
.(For this particular case, the source channel is important because
conda-forge::libxcb
depends onxorg-*
packages and as such is usable in base-minimum containers, whereasdefaults::libxcb
uses CDT packages and thus is not usable in self-contained environments.)Below are the complete package lists from
mamba create
andconda create
, resp., for comparison:$ mamba create -dqnx -c conda-forge graphviz=2.42.3=h6939c30_1 2>/dev/null
$ conda create -dqnx -c conda-forge graphviz=2.42.3=h6939c30_1 2>/dev/null
(cc @FelixMoelder who encountered this in the
snakemake/snakemake:v5.26.1
container image.)The text was updated successfully, but these errors were encountered: