Conda 4.7.5 fails to solve environment that Conda 4.6.11 solves #8844
Comments
|
Here's a hint generated by the latest master branch: I don't fully understand it yet. There's a lot of noise. One thing that stands out to me is that there's a mix of stuff that uses libgcc and libgcc-ng. Those two should never be installed together. They overlap filenames and will break one another. I think the fundamental reason for the breakage is that conda 4.7.x drops the "free" channel. Indeed, adding that back in fixes things:
Those things that depend on libgcc really, really need to be rebuilt. |
msarahan
added
¡breaking!
|
re: libgcc and libgcc-ng — if they shouldn't be installed together it sounds like we need them to depend on a mutex package... I've seen this in other environments too and wondered if that was going to get me into trouble... |
|
conda update conda 4.7.5 |
|
Thanks for the help with this, @msarahan I just wanted to additionally confirm that your solution of |
|
I'm having a similar issue after updating to conda 4.7.5, but it's even worse. I can't downgrade conda, I can't update/install/uninstall any package (get similar UnsatisfiableError, but with a different list of packages), and I cannot revert back using conda install -revision. It feels like updating essentially broke my build. What can I post to help debug my case? (I've never posted to boards like these before, so I'm not sure what is the proper way to do this. Apologies in advance.) |
|
Sorry, it is especially frustrating to feel stuck. Some users have reported success reverting to an earlier revision. The commands to do this look like:
This website talks about it more: Since you can't run We have fixed a lot of the issues, and you can also try to update conda. Given your current state, it's probably best to download the latest conda release manually from https://anaconda.org/conda-canary/conda/files - choose the file for your OS and python version. Try to install that with If that doesn't work, extract that file manually into your anaconda/miniconda installation, overwriting the existing conda files there. |
|
Thanks for the response! Yes, I have already tried both of those options, except for extracting it manually. I will try that and let you know. |
|
Edit 2: Okay, the installation worked, but I made the mistake of trying
Now I get this when running conda list: Error processing line 1 of C:\Users\Kiret\Anaconda3\lib\site-packages\protobuf-3.4.1-py3.6-nspkg.pth: Traceback (most recent call last): Remainder of file ignored During handling of the above exception, another exception occurred: Traceback (most recent call last): Edit: Sorry, dumb mistake by forgetting to switch back to base before install. Let me try it again and update you. Leaving the original below in case it helps anyone (e.g., by allowing them to say, "well, at least I'm not as nooby as that guy").Okay, I was able to install 4.7.7 manually. That led to 'ImportError: No module named ruamel.yaml.comments' on conda list (or any conda command i tried). I tried manually installing ruamel_yaml, which the error asked me to do. That gives me this next error: from conda_package_handling.api import InvalidArchiveError Would you suggest this should be pretty easy to fix from here? Or is this unexpected behaviour? |
|
After that install, I can no longer open Anaconda Prompt or Anaconda Navigator. Time for a fresh install...? |
I also suddenly started having trouble with my Anaconda version 4.7.5 and it sounds like a similar issue to what @kiretd is facing. I tried going back to a previous revision that was working and got the following error: root@joecloud:~# conda install --revision ##
environment variables: populated config files : |
|
I am having a similar problem. I have not been able to do anything with conda since updating to version 4.7.5, and some of the packages I previously installed are no longer working. When I tried installing a revision before conda was updated from 4.6.14 to 4.75, I got the following error: >>>>>>>>>>>>>>>>>>>>>> ERROR REPORT <<<<<<<<<<<<<<<<<<<<<<
environment variables: populated config files : /home/ikaplow/.condarc An unexpected error has occurred. Conda has prepared the above report. I also get an error when I try to downgrade conda. Please let me know what I can do to fix this. Thanks so much! |
|
@msarahan I also got an error after
I tried downloading conda-4.7.7-pyXY_0.tar.bz2 as you suggested. After doing Please help! |
|
I'd just like to provide an update for the issues I was having. I managed to fix all of my issues by getting rid of my anaconda/miniconda directories ( |
|
I am not using miniconda, so I do not think that will work for me. I also installed a lot of packages with anaconda, so I would prefer not to have to reinstall everything from scratch. I tried installing conda 4.7.7, and I have no idea if that worked. I have been waiting for over an hour to solve the environment to install a new package (I used to wait 3-5 minutes), so I have no idea when I will find out if it works. |
|
Thank you @joeborrello I did the same with Anaconda. |
|
After a lot of trial and error, I finally got anaconda and almost all of the packages I had previously installed to work again. I did it by downloading conda 4.6.14 from https://anaconda.org/conda-canary/conda/files?page=2 and then running conda install /home/ikaplow/conda-4.6.14-py27_0.tar.bz2, which got me back to conda version 4.6.14 (everything was working with that before I upgraded to conda 4.7.5). |
|
Update on issue with 4.7.5 (main issue): After doing some further digging, we finally found that two of our dependencies (dde, theano) explicitly required the following packages between the two of them:
Looking at the environment that 4.6.11 built, these packages were still downloaded, but conda was able to find these packages from the Free channel. Once the Free channel was removed as a default in 4.7, conda was no longer able to find these packages unless we restored the free channel or added the Anaconda channel where these packages can also be found (this was our first solution to the problem). We also updated all of our packages so that nothing depends on libgcc anymore and instead depends on libgcc-ng. While this likely helped us avoid issues for the future, this alone would not fix our issue, as conda still needs to be able to find the three packages listed above. Given all of this, the solution to all of this is simply to read the documentation on the free channel listed here. I'll go ahead and close this issue as everything seems to be solved now. |
|
Thanks for the information! I have been using theano, so this might explain why conda 4.7.5 was not working for me. |
|
Rollback your conda environment (conda 4.7.10 --> 4.6.11) |
|
Was getting similar errors, confirmed fix by downgrading conda
using conda-4.6.11-py37_0.tar.bz2 |
|
running |
|
Hi there, thank you for your contribution to Conda! This issue has been automatically locked since it has not had recent activity after it was closed. Please open a new issue if needed. |
Current Behavior
Trying to build a conda environment from an environment file with
conda env create -f environment_linux.ymlwith conda 4.7.5 fails to solve the environment with ResolvePackageNotFound. However, doing the exact same thing on the same environment file works without any errors using conda 4.6.11.Interestingly though, if we explicitly list the packages in the environment file that ResolvePackageNotFound complains about, then conda 4.7.5 builds the environment just fine.
Steps to Reproduce
Run the following command
conda env create -f environment_linux.ymlon the following environment file:Doing this with conda 4.6.11 runs just fine, but doing this with conda 4.7.5 yields the following error message:
See also a Pull Request where this issue is discussed on RMG-Py here
Again, note that adding pydot-ng and pygpu to the environment file fixes this issue in 4.7.5, but this was not necessary for conda 4.6.11
Expected Behavior
Conda 4.7.5 should be able to solve the exact same environment file as conda 4.6.11
Environment Information
`conda info``conda config --show-sources``conda list --show-channel-urls`The text was updated successfully, but these errors were encountered: