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
Multiple package resolutions - how to resolve? #7173
Comments
Can you provide the output of |
It's possible we have a packaging issue here. It appears that @nehaljwani built I wasn't able to find the quandl recipe at https://github.com/AnacondaRecipes. However, lookin in https://repo.continuum.io/pkgs/main/linux-64/repodata.json, I'm seeing
and in comparison, from https://repo.continuum.io/pkgs/free/linux-64/repodata.json
So the new package adds an upper bound to the requests dependency, and that upper bound should be patched onto the other quandl packages I'm guessing. |
conda info
|
I've meet the same issue.
|
hi, do anyone resolve this issue? |
I had this issue as well, but it seems to have been resolved now. |
I had to do |
Seems that this issue appeared again... |
Does anyone really know how to solve this issue with Multiple package resolutions?
conda info:
|
@Selena-21 The |
I'm getting this issue. Did a `Warning: >10 possible package resolutions (only showing differing packages):
|
Getting the same warning with latest conda. (base) C:\Users\demircan>conda update --all
All requested packages already installed.(base) C:\Users\demircan>conda info
populated config files : C:\Users\demircan.condarc |
Hi. Receiving the same issue as bdemircan. However, the platform is linux-64.
Any assistance would be greatly appreciated. |
Same issue with nbconvert for me, platform is osx-64. Additionally, I get the attached warning in spyder. If someone could help resolving this, I would be grateful. `conda update --all
All requested packages already installed.``conda info
populated config files : /Users/au588006/.condarc |
The problem is that old builds of nbconvert do not put any constraint on their pandoc version. New ones do. The solver is forced to choose between newer nbconvert or newer pandoc, and they're mathematically equivalent here. We need to fix our repo data, so that all nbconvert builds have an upper bound for pandoc. |
@msarahan, Jupyter guys decided to increase the upper level of Pandoc to Older versions should use |
conda-forge has removed the upper bound from the pandoc requirement in the nbconvert recipe, conda-forge/nbconvert-feedstock#28. I'll release a package to |
A new |
Hi. Just performed a
Now after the installation of the packages and performing another
Thank you very much and I appreciate the help! |
This solved the issue for me, thanks a lot! |
Hi. I have the same issue as tested today:
Sadly,
Here is my
Could you please help me in solving this issue? Many Thanks |
You can use this following command this one resolved my issue |
strict-channel-priority didn't fix it for me. Output:
conda info:
|
I have the same issue conda info:
conda update --strict-channel-priority --all:
|
when i downgrade conda from 4.7 to 4.6, everything goes well ! |
I have these warnings:
conda info
downgrading to conda 4.6 with this command |
conda 4.7 still have the same problem
|
conda 4.8.0 still have this issue, maybe this is acceptable
All requested packages already installed.(base) ➜ ~ conda --version |
I just reinstalled Anaconda on Win 10 and have the same problem as many above. Different to some others in my case the channel is always
Question: Should running any of the below lines NOT show the "package resolutions" when running the code (BEFORE), or only AFTER an update was done. I am assuming it is BEFORE, but that has not been clear. When I run the below lines I still see the package resolutions issues, so I do not execute them at the y/n junction. conda info (for an environment)
|
The multiple solution between jupyter_console and prompt_toolkit has been fixed in AnacondaRecipes/repodata-hotfixes#62 |
I've been experiencing this problem for several weeks after
I'd appreciate clarification/advice on the best way forward. -Tom
|
'''
All requested packages already installed.(base) C:\Windows\system32>conda info
populated config files : C:\Users\qtckp.condarc |
Thank you, @msarahan ! Yours was the only comment in this thread that actually explained what was happening so that I understood whether or not to worry about this. I was finding the issue with The truly useful answer, therefore, is to explain the underlying mechanic: there are two potential repos, each of which are equivalently "correct" because one is further ahead for one dependency and the other is further ahead for another. In my case, I am assuming "all is good", but if I have a problem, now I know I can force the other repo to be chosen (or I can force a particular version of a dependency). People should not "thumbs up" other complaints or problems... it challenges others in tracking down the truly useful answers like what Mike provided above. |
You should go to your anaconda directory, anaconda3/pkgs and look for the resolution you want to delete, I delete low versions actually. |
From @lifescholar on November 7, 2017 9:49
I'm receiving the following warning on issuing the 'conda update --all' command:
Warning: 2 possible package resolutions (only showing differing packages):
- defaults::quandl-3.2.0-py36h30f7a5e_0, defaults::requests-2.14.2-py36_0
- defaults::quandl-3.1.0-py36_0, defaults::requests-2.18.4-py36h4371aae_1
Is this as a result of a bug, or is there a way to resolve it?
Copied from original issue: conda/conda#6273
The text was updated successfully, but these errors were encountered: