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
package conflict messages not understandable #9707
Comments
I was just on my way here to file a similar issue, but found this one first. I too have been fighting with solver issues, and the messages leave me unable to tell if the solver is misbehaving or if I'm making an error somewhere. Here are a couple of very typical examples:
What is that trying to tell me? Is there a reference somewhere that could help in interpreting these messages? |
same here on Ubuntu 18.04, conda 4.8.4:
Nothing seems incompatible though... |
Has there been any progress on this? I run into this issue often and it's cost me lots of time recently.
Ah, so it found conflicts but no specifications were found to be incompatible with each other? Not even any false positives like usual. Fantastic. |
+1 on this, because it's terribly frustrating when all listed conflicts don't look like conflicts at all:
or
|
How can there be no dev available to explain this confusing behaviour? Is there no documentation on this? |
How can this throw a conflict? |
I just spent all day on this kind of rubbish, and have got absolutely no-where. Clearly a lot of effort has gone into conda, but unfortunately it seems kind of useless for anything non-trivial..... |
Yes. So redundant given all the other comments. Why has nothing been done? |
Same issue. |
My life is very miserable now.
Update: for anyone who is looking for a conda alternative, mamba works flawlessly. |
Hey all, just to give some context why this hasn't been obvious, the previous conda maintainers left Anaconda in 2020 and a new group of people have started earlier this year (including me). We're currently in the process to port the mamba/libsolv solver to conda which should improve the user experience drastically in many areas, just like reporting of conflicts. More on that soon! |
Just my luck. I'm trying to find an issue where a new package is causing thousands of lines of conflicts and man, I don't know where to start. I hope 5.0.0 comes out soon to resolve this. |
@EricAtORS have you tried mamba? |
Very interesting project. |
I cant even install mamba due to frustrating conflicts. Why don't they finally add an "override" function for such errors and save so many users from such a waste of time. |
I created a fresh environment with It tried to resolve conflicts for well over an hour, then eventually printed a list of conflicts so long I couldn't even scroll to the top of it in my terminal. Problem is most of the conflicts don't even make sense. I've got hundreds of examples of this issue now. Based on #9136 it seems these are probably just missing the requirement actually causing the conflict. Here is the output (as I explained the top is cut off): Edit: Seems my specific issue was probably that the second command was run in the base envrionment, not the new one. The point about the confusing conflict messages remains though. |
For me the solution was to use |
Hi there, thank you for your contribution! This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs. If you would like this issue to remain open please:
NOTE: If this issue was closed prematurely, please leave a comment. Thanks! |
Current Behavior
Messages printed when conflicts prevent creating an environment show what does not seem like a conflict:
Why wouldn't e.g. xz=5.2.4 satisfy these constraints?
Also, the conflict messages printed are non-deterministic, showing different conflicts every time the command to create the environment is re-run.
Steps to Reproduce
Expected Behavior
Print a message that will enable me to fix the conflict.
Environment Information
`conda info`
`conda config --show-sources`
`conda list --show-channel-urls`
The text was updated successfully, but these errors were encountered: