-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
solver not pulling latest build #44
Comments
Note that mamba seems to come to a different solution
I think this is because mamba always maximizes build number ahead of other things? @wolfv any comments here? |
A workaround for this issue is to use strict channel priority. |
strict channel priority does not appear to solve this issue
in otherwords, the offending builds are ours. cc @isuruf |
yep, mamba always prefers higher build numbers if there is no conflict. |
Ahhhhhhh! Thank you @isuruf! |
To reproduce @leofang's issue, you need to add |
Right. I do think the separate issue here matters though. Any thoughts? |
I agree, but that's not the most pressing issue right now. |
Sure. I am not in a rush either. I just wanted to make sure this issue should remain open. |
Issue:
The solver doesn't appear to pull the latest build
Here is what is available.
When you specify
gcc_impl_linux-64=7.5.0
at the command line, it works correctly.Note that builds past 13 have extra and more complicated deps due to the cross-compiling PRs.
The columns here are the package, constrains and depends.
Environment (
conda list
):Details about
conda
and system (conda info
):The text was updated successfully, but these errors were encountered: