Conda install stuck on solving environment

After re-imaging my machine I find that conda freezes at 'Solving package specifications' when re-installing mageck-vispr. Did anyone manage to solve this issue? I'm using Miniconda3 based on Python 3. Then I'm trying to install in a new environment by:. This seems to be an issue in conda. It seems that they are still working on solving this bug see the discussion here.

Based on their discussion, the best way is to remove r channel from conda although it does not guarantee to solve the problem. Follow the instruction here. I tested it just now and it works by removing the r channel. So it's closed but let me know if there are still further problems.

Hello Wei Li, I tried to follow the instructions at the link you provided, but could not figure it out. It still hangs and I'm unable to install the environment to work with mageck-vispr.

Fabrication cost estimation xls

Issue 26 resolved. Hi there. Thanks for developing this excellent tool. Current conda install: platform : osx conda version : 4.

conda install stuck on solving environment

Comments 7 You may need to add several channels using the following code: conda config -- add channels defaults conda config -- add channels conda - forge conda config -- add channels bioconda. Then I'm trying to install in a new environment by: conda create - n mageck - vispr mageck - vispr. Current conda install : platform : linux - 64 conda version : 4.

I also encountered the the same problem. I found a way to work around this conda create -n mageck-vispr bismark source activate mageck-vispr conda install mageck-vispr.GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account. You cannot mix conda forge and Anaconda defaults in the same environment. I'm having a similar issue; however this is happening without the --all flag, which makes me wonder if I should report it as a different issue. Exact same issue.

Odr bridge wifi technicolor

It hangs completely when doing update all, although update package does complete, albeit updates sometimes fail. The anaconda3 folder is 4. Skip to content. Dismiss Join GitHub today GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.

Sign up. New issue. Jump to bottom. Copy link Quote reply. I'm submitting a Expected Behavior I expect all my packages to update. JustGottaCAT changed the title conda update stuck at "Solving environment" conda update --all stuck at "Solving environment" May 9, This comment has been minimized. Sign in to view. Can one mix anaconda "defaults" and "conda-forge" channels in an evironment My situation I'm having a similar issue; however this is happening without the --all flag, which makes me wonder if I should report it as a different issue.

My procedure When I update conda and anacondaI do so with these commands: For conda : conda update conda -c defaults For anaconda : conda update anaconda -c defaults My trace results For debugging purposes, I ran the following command: conda update conda -vvv -c defaults I let it run for a short while, and this is what caught my eye: Here's the output of conda update conda -vvv -c defaults DEBUG conda.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment. Linked pull requests.Creating an environment with commands.

Creating an environment from an environment. Specifying a location for an environment. Updating an environment. Building identical conda environments. Activating an environment. Deactivating an environment.

Determining your current environment. Viewing a list of your environments. Viewing a list of the packages in an environment. Using pip in an environment.

Subscribe to RSS

Setting environment variables. Saving environment variables. Sharing an environment. Restoring an environment. Removing an environment. Switching or moving between environments is called activating the environment. You can also share an environment file.

There are many options available for the commands described on this page. For details, see Command reference. For conda versions prior to 4. Windows: activate or deactivate. Linux and macOS: source activate or source deactivate.

Gt power aircraft sound system

By default, environments are installed into the envs directory in your conda directory. See Specifying a location for an environment or run conda create --help for information on specifying a different path. Replace myenv with the environment name. When conda asks you to proceed, type y :.

conda install stuck on solving environment

This environment uses the same version of Python that you are currently using because you did not specify a version. Install all the programs that you want in this environment at the same time.By using our site, you acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service. The dark mode beta is finally here. Change your preferences any time.

Stack Overflow for Teams is a private, secure spot for you and your coworkers to find and share information.

packages in environment at /Users/danofer/anaconda3:

Good evening, i run Ubuntu I've installed Anaconda 5. Yesterday i've waited for about 4 hours before giving up. I would like to know if there is a known issue about this problem and if it can be related to the quantity of disk and RAM i have assigned to the virtual machine. Thanks in advance. I will write a more general solution, to Conda's "Solving Environment" issue, which I had the uttermost pleasure with. When conda seem stuck it is possibly having too many options or some conflicts resulting in the SAT solver getting clause counts of multiple millions.

If it stays at one of these lines for long time, then try specifying version for packages as above. If there seem another issue, try the conda GitHub.

conda install stuck on solving environment

Learn more. Asked 1 year, 6 months ago. Active 1 year ago. Viewed 9k times. Paolo Paolo 1 1 silver badge 3 3 bronze badges. My conda is hanging on Solving environment when I try to install something from the conda-forge channel. I'm not sure why. Active Oldest Votes. I had the same issue but then I updated Conda and it worked Think twice before you do it! I have the same problem on macOS I, too, had the same problem: conda was hanging for more than 12 hours!By using our site, you acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service.

Stack Overflow for Teams is a private, secure spot for you and your coworkers to find and share information. I can not use the conda utility anymore. I tried to look at my. Do you know what I can do to go back to a working conda? And with a ranting hat on: This is the third time in the space of about 18 months that a conda update has resulted in an error that causes builds to fail, and there's been plenty of other issues too.

I presume it will be fixed by the core conda people at some point, and maybe it is caused by a particular combination of third party dependencies, but one way or another conda always seems extremely buggy. There was once an update that caused conda install conda to delete itself!

This problem is still out in the field - started happening to me on a fresh Windows 10 install with latest stable Anaconda Getting 'Solving environment: failed' on 'conda install -c conda-forge xgboost' command. I could install something from the base channel eg. I was facing the same problem with the Anaconda 3 ver. So what I did is that I used Anaconda prompt. It automatically links the base conda files to the required proxies.

Then type "conda install numpy". This will solve it in Windows. I got the same problem and solved. In Anaconda promptuse pip install scpnot conda install scp. I have tried to solve this problem for some time now. Finally I figure out that you should use pip install instead of conda install. Normally we use pip install in windows command prompt and conda install in Anaconda Prompt.GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Simplicity zt 16 44 for sale

Already on GitHub? Sign in to your account. I'm seeing the same - also with the intel channel, though not conda-forge. Dropping defaults and just using "main" seems to have helped.

Speed dating midland mi

I experienced similar issue installing cuda development packages to fresh install - fixed it by creating new environment and activating it then installing new packages there without issue. If you can limit yourself to just some of those you may be able to speed up the depsolving.

But this is still a huge pain for us - I see conda update all in a python2 environment taking between 30 and minutes on fast hardware. Still solving environment.

I had the same problem. I cancelled the installation and used the conda navigator instead: anaconda-navigator. I have the same problem: "solving the enviroment" is still continuing after 40 minutes. Moreover, I cannot use anaconda-navigator but this is another problem or not? I observe also which has been closed for commenting. I understand this is one priority issue for the development team. For solve times beyond one or two minutes, it is almost always some problem with metadata that leads conda into awkward loops where there is not a clear "right" answer.

For example, things on defaults are built with openssl 1. Because conda-forge doesn't have a complete set of packages using openssl 1. Strict channel priority is helpful for forcing these situations to error out quickly instead of churning, though the error messages are not always very helpful. If you identify packages that create problems, it is helpful to file issues using the "speed complaint" template. Even if there's nothing conda can do, we can perhaps help fix the metadata in our packages or on conda-forge so that other people don't get stuck.

I had this exact problem. But then I created an empty env and went into it to run the same command, it let me install it after a short wait. I'm starting to think that dropping all default channels and only using conda-forge might be the only solution. It's weird if you think about it -- using Anaconda but not using Anaconda official channels -- but nowadays I find myself uninstalling and reinstalling complete envs just because I want one additional package and solver for conda install I have a talk on this at Anacondacon.

Hopefully the recording will be up soon and hopefully I can put my slides up somewhere. Using --strict-channel-priority seems to help me out a lot with speed. Though it's going to require reworking how I've configured various environments.GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Steps to reproduce

Already on GitHub? Sign in to your account. Conda 4. The problem appears to be new. I first encountered it several days ago when trying to create a new environment containing the phyloflash recipe, and have since have heard reports from other users, and also reproduced the problem on a virtual machine with a fresh miniconda install.

It was still able to solve the environment on Whereas it is able to solve the environment if I attempt to create an environment containing the dependencies specified in the bioconda recipe:. Following the suggestion in issueI removed conda-forge from the channels list and it was able to solve, suggesting that the issue lies there. While I can install the software with this workaround, it is not ideal because the Bioconda docs recommend giving conda-forge priority, so most users would have it set up like this.

The information that you have provided suggests that there is a metadata problem between conda-forge and bioconda and maybe also including defaults.

By putting all of your dependencies in explicitly, you are dramatically changing the problem that you're asking conda to solve. You might not realize it, but conda treats explicit specs very differently from implicit ones.

I think you need to approach this as a problem with your channel metadata, and work with the conda-forge and bioconda communities to address it. If you find a repeat pattern that you think conda should handle better, please let us know.

Thanks msarahan for the detailed explanation, it has helped to demystify somewhat what is going on under the hood. Setting strict channel priority appears to work for the moment, but I guess this sort of problem will take some time to fix, if the broader issues are poorly-constrained dependencies and missing metadata, if I've understood correctly. Hey this exact problem happened to me earlier and changing that priority fix it.

Shouldn't that flag be set by default or something? In a fresh conda install with a fresh Ubuntu Skip to content. Dismiss Join GitHub today GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.

Sign up. New issue. Jump to bottom. Copy link Quote reply.


thoughts on “Conda install stuck on solving environment

Leave a Reply

Your email address will not be published. Required fields are marked *