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

Solving environment: failed with repodata #225

Open
PedroDaPos opened this issue Mar 5, 2021 · 1 comment
Open

Solving environment: failed with repodata #225

PedroDaPos opened this issue Mar 5, 2021 · 1 comment

Comments

@PedroDaPos
Copy link

Hello! I was wondering if you could help me figuring out what is the solution for the following error messages. I am following instructions to install dammit via conda, but it initially gives me the following messages:

Collecting package metadata (current_repodata.json): done Solving environment: failed with initial frozen solve. Retrying with flexible solve. Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source. Collecting package metadata (repodata.json): done Solving environment: \

Sometimes it stays in the "solving environment" state for hours. Then I get this error message:

`Found conflicts! Looking for incompatible packages. failed

UnsatisfiableError: The following specifications were found to be incompatible with each other:

Output in format: Requested package -> Available versions`

I updated conda, and even downgraded conda, but was still not able to solve this problem. I was wondering if perhaps this is an issue others may have experienced. Any solution or advice on how to resolve this issue would be greatly appreciated. Thank you in advance!

@camillescott
Copy link
Member

Thanks for the report @PedroDaPos! So one issue with dammit v1.x is that the required conda environment is.... reallllly big. So big, that sometimes the dependency solver just gives up -- this especially happens if you try to install dammit into an existing conda environment, as opposed to creating a new conda environment.

The most direct solution is to conda install -c conda-forge mamba in your base environment, and then use mamba instead of conda to install dammit. mamba is a reimplementation of conda in pure C++, with a more efficient dependency solver, and it's MUCH faster than regular conda.

The other solution is wait a couple weeks for when we've pushed out dammit v2, which uses Snakemake and per-task environments, sidestepping the giant tangled environment altogether.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants