Skip to content
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

What does it mean when when conda refuses to install and doesn't offer a resolution? #5255

Closed
abalter opened this issue May 9, 2017 · 3 comments
Labels
locked [bot] locked due to inactivity solver::messaging pertains to the solver's messaging source::community catch-all for issues filed by community members stale::closed [bot] closed after being marked as stale stale [bot] marked as stale due to inactivity type::feature request for a new feature or capability

Comments

@abalter
Copy link

abalter commented May 9, 2017

Most of the time when conda runs into a conflict it will show you a resolution and ask how you want to proceed. This is how I would expect a package manager to act. That is what apt does. But sometimes I get something like:

balter@BICB260:~$ conda install r-venndiagram
Fetching package metadata ...................
Solving package specifications: .


UnsatisfiableError: The following specifications were found to be in conflict:
  - r-backports
  - r-venndiagram -> r 3.2.2* -> r-base 3.2.2
Use "conda info <package>" to see the dependencies for each package.

It would be nice if conda would offer some possible resolutions.

@abalter abalter changed the title What does it mean when when conda refuses to intall and doesn't offer a resolution? What does it mean when when conda refuses to install and doesn't offer a resolution? May 9, 2017
@kalefranz
Copy link
Contributor

I agree. There are tons of open issues that look very similar to this one. Definitely high priority on the list of improvements, if nothing else to cut down on the number if issues being filed :)

I'm guessing here r-venndiagram needs r version 3.2.2*, but r-backports is already installed, and it's incompatible with that version of r. So what you probably need to do is uninstall r-backports, and then let conda upgrade your version of r.

@kalefranz kalefranz added source::community catch-all for issues filed by community members solver::messaging pertains to the solver's messaging type::feature request for a new feature or capability labels May 9, 2017
@github-actions
Copy link

github-actions bot commented Aug 19, 2021

Hi there, thank you for your contribution to Conda!

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:

  1. Verify that you can still reproduce the issue in the latest version of Conda
  2. Comment that the issue is still reproducible and include:
  • What version of Conda you reproduced the issue on
  • What OS and version you reproduced the issue on
  • What steps you followed to reproduce the issue
  1. It would also be helpful to have the output of the following commands available:
  • conda info
  • conda config --show-sources
  • conda list --show-channel-urls

NOTE: If this issue was closed prematurely, please leave a comment and we will gladly reopen the issue.

In case this issue was originally about a project that is covered by the Anaconda issue tracker (e.g. Anaconda, Miniconda, packages built by Anaconda, Inc. like Anaconda Navigator etc), please reopen the issue there again.

Thanks!

@github-actions github-actions bot added the stale [bot] marked as stale due to inactivity label Aug 19, 2021
@github-actions
Copy link

Hi again!

This issue has been closed since it has not had recent activity.
Please don't hesitate to leave a comment if that was done prematurely.

Thank you for your contribution.

@github-actions github-actions bot added the stale::closed [bot] closed after being marked as stale label Nov 19, 2021
@github-actions github-actions bot added the locked [bot] locked due to inactivity label Nov 19, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked [bot] locked due to inactivity solver::messaging pertains to the solver's messaging source::community catch-all for issues filed by community members stale::closed [bot] closed after being marked as stale stale [bot] marked as stale due to inactivity type::feature request for a new feature or capability
Projects
None yet
Development

No branches or pull requests

2 participants