CODEWITHSUNDEEP
pythonanacondaconda
J.D
J.D

Reputation: 1971

Conda install and update do not work also solving environment get errors

I am using anaconda as below:

(base) C:\Users\xxx>conda info

     active environment : base
    active env location : C:\Users\xxx\Documents\ANACONDA
            shell level : 1
       user config file : C:\Users\xxx\.condarc
 populated config files : C:\Users\xxx\.condarc
          conda version : 4.7.11
    conda-build version : 3.18.9
         python version : 3.6.9.final.0
       virtual packages :
       base environment : C:\Users\xxx\Documents\ANACONDA  (writable)
           channel URLs : https://repo.anaconda.com/pkgs/main/win-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/free/win-64
                          https://repo.anaconda.com/pkgs/free/noarch
                          https://repo.anaconda.com/pkgs/r/win-64
                          https://repo.anaconda.com/pkgs/r/noarch
                          https://repo.anaconda.com/pkgs/msys2/win-64
                          https://repo.anaconda.com/pkgs/msys2/noarch
          package cache : C:\Users\xxx\Documents\ANACONDA\pkgs
                          C:\Users\xxx\.conda\pkgs
                          C:\Users\xxx\AppData\Local\conda\conda\pkgs
       envs directories : C:\Users\xxx\Documents\ANACONDA\envs
                          C:\Users\xxx\.conda\envs
                          C:\Users\xxx\AppData\Local\conda\conda\envs
               platform : win-64
             user-agent : conda/4.7.11 requests/2.22.0 CPython/3.6.9 Windows/10 Windows/10.0.16299
          administrator : False
             netrc file : None
           offline mode : False

Now I have 2 issues that stop my work. 1) I cannot use conda install for any package. It will give me the error in solving environment list this:

failed with initial frozen solve. Retrying with flexible solve.

then it will fail again and give message like this:

Found conflicts! Looking for incompatible packages.
This can take several minutes.  Press CTRL-C to abort.

Even after the checking for incompatible packages, it didn't give me the solution.

2) When I want to upgrade or downgrade conda by the command:

conda update -n base conda

or

conda install conda = 4.6.11

It will give me errors again in the solving environment, and I think this is related to the first issue.

Now I cannot use conda for anything, please advise and thank you!

Upvotes: 106

Views: 294130

Answers (13)

prerakmody
prerakmody

Reputation: 116

On Rocky Linux 8.10, I had to update my conda itself from 4.9.2. These were the steps I took.

HISTORY

  • 4.9.2 --> 4.8.3 [works]
  • 4.8.3 --> 24.5.0 [failed due to conflicts]
  • 4.8.3 --> 4.14.0 [works]
  • 4.14.0 --> 23.1.0 [failed due to conflicts]
  • 4.14.0 --> 24.5.0 [works, after update --all and mamba-solver]

On 4.9.2

  • conda install --rev 0 [worked, setting to default of 4.8.3]

On 4.8.3

  • conda install conda==4.14.0 [worked]

On 4.14.0

  • conda install conda==23.1.0 [failed due to conflicts]
  • conda install -n base conda-libmamba-solver [failed due to conflicts]
  • conda update --all --yes [works]
  • conda install -n base conda-libmamba-solver [worked after update --all]
  • conda install conda==24.5.0 --solver=libmamba [worked]

My recommendation for others would be

conda install --rev 0 # to remove all extra packages so that solver can run fast
conda install -n base conda-libmamba-solver # for faster resolution of packages
conda install conda==24.5.0  --solver=libmamba # from 23.10.0 libmamba is the default solver
# OR
conda update conda   --solver=libmamba

Upvotes: 0

Daniele Gentili
Daniele Gentili

Reputation: 611

As stated by a Conda maintainer in https://github.com/conda/conda/issues/8051#issuecomment-1549451621 their official position is that they know the old solver is slow and that is why they put effort in allowing the libmamba solver to be used in Conda.

To install:

conda install -n base conda-libmamba-solver

at which point you are free to use it once, e.g.:

conda install tensorflow --solver=libmamba

or set as default solver:

conda config --set solver libmamba

It usually solves in seconds.

For more installation info see: https://conda.github.io/conda-libmamba-solver/getting-started/

Upvotes: 3

J B
J B

Reputation: 440

I've generally had good results with conda and pip, but learned over time that environments really can get broken by unusual combinations of packages, and just starting a new env from scratch is often the only way forward. In my case it was tensorflow-gpu that wouldn't install from conda-forge, into an env I'd already been using for some weeks. The list of packages cited as being incompatible was in the dozens. I tried all the things listed on this page, but in the end I just hammered out a new env. Since I was deducing what packages I needed to install in the new env by running my program and installing one package at each error (ie instead of being methodical about listing my former env), along the way I reproduced this frozen solve thing several times. Each time it happened, I shuffled that conda package back to the initial conda create command and started again. Eventually my program ran in the new env, with tensorflow-gpu imported, and the root cause was revealed as conda installs which occur after pip installs. It wasn't anything to do with conda version or conda config.

A specific note for anyone using opencv-python, I ended up needing to install qt via conda, before attempting to install opencv-python via pip. That was a tricky one because it's a runtime error, and on stack overflow many of the solutions refer to various qt lib requirements which aren't part of python/conda and which I already had.

A further specific note. Some pip installs will roll back a version of a related package, thus breaking other conda-installed packages. In my case the example was a package called peakutils rolling back numpy, which then broke a from numpy import ma in scale.py module in the matplotlib package. My head is still spinning.

Upvotes: 1

teksoy
teksoy

Reputation: 27

I had same problem but I solved because of SKİD.

After you create new env, You can run one of the codes in this link.

https://anaconda.org/rdkit/rdkit

Upvotes: 1

Rosario Scavo
Rosario Scavo

Reputation: 517

I solved a similar problem by doing the following:

conda update --all --yes

Upvotes: 26

Taewon
Taewon

Reputation: 143

Recommend to upgrade conda latest version.

conda install --quiet --yes conda=4.7.11 
python -m pip install --upgrade pip==19.2.2

Upvotes: -3

exan
exan

Reputation: 3925

I started running in to this problem when one package suggested following modifications before installation

conda config --set channel_priority true

so I just reverted it and voila error's gone

conda config --set channel_priority false

Upvotes: 60

Thomas
Thomas

Reputation: 10055

I run into same problem while installing geopandas. The issue was gone after I upgraded to a newer version of Anaconda using:

conda update --prefix C:\apps\anaconda3 anaconda

Note: you'll have to modify the path C:\apps\anaconda3 pointing to your own installation directory.

Strangely, I did download Anaconda from the official homepage just a few hours ago and thought I had the newest version...

Upvotes: 1

Prox
Prox

Reputation: 894

https://stackoverflow.com/a/61117831/7802476 helped me. Creating a new environment using the accepted answer didn't get my jupyter notebook to recognize the installed opencv. I could only import cv2 when I was in the environment on my terminal.

The fix was to use pip instead of conda, pip install opencv-python

Upvotes: 1

Guru
Guru

Reputation: 69

If your conda version is greater than or equal to 4.8, you may see that error. 

(base) [localhost ~]$ conda --version
conda 4.8.2
(base) [localhost ~]$ conda install -c anaconda requests-kerberos
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.

Downgrade your conda if possible using the following commands

conda config --set allow_conda_downgrades true
conda install conda=4.6.14

Then create your virtual environment:

conda create --name myenv_conda

Then activate your myenv_conda

conda activate myenv_conda

Now try to install packages using conda -c install anaconda 

eg: conda install -c conda requests-kerberos

output:
(myenv_conda) [localhost ~]$ conda install -c anaconda requests-kerberos
Collecting package metadata: done
Solving environment: done
....
....
....
Preparing transaction: done
Verifying transaction: done
Executing transaction: done

Upvotes: 4

SKiD
SKiD

Reputation: 1134

I ran into the same problem and I couldn't find a solution, but I did find a workaround. If you create an env and activate that env and then do the install, it seems to work just fine. If you don't need a lot of libraries I would try that.

Commands are:

  1. Create env
conda create --name myenv
  1. Activate the env
conda activate myenv

Upvotes: 101

Rochan
Rochan

Reputation: 1542

Create a new environment if your are not superuser, after that activate environment to install packages

Upvotes: -1

Abhyudai
Abhyudai

Reputation: 924

You may downgrade to an older version of conda 4.6.14 and then install your packages.

conda config --set allow_conda_downgrades true
conda install conda=4.6.14

Upvotes: 5

Related Questions