search

conda-forge / scikit-image-feedstock

A conda-smithy repository for scikit-image.
BSD 3-Clause "New" or "Revised" License
4 stars 25 forks source link

Conda has problems resolving dependencies in fresh environment #94

Closed raphaelquast closed 1 year ago

raphaelquast commented 1 year ago

Solution to issue cannot be found in the documentation.

Issue

re-posting here as suggested (original issue: https://github.com/scikit-image/scikit-image/issues/6591)

I realized that installing scikit-image with conda in a fresh environment takes a very long time and it seems that conda has problems solving the environment (even though it's completely fresh)

To sort out any problems with conda on my side I did a quick fresh install of miniconda, created a new environment and tried again... still getting the same result.

Not sure if this is really a bug or not but I thought it might be worth reporting it

Way to reproduce:

conda create -n new_env python=3.7
conda activate new_env
conda install -c conda-forge scikit-image

>>> 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.
>>> ...

Installed packages

ca-certificates           2022.07.19           haa95532_0
certifi                   2022.9.24        py37haa95532_0
openssl                   1.1.1q               h2bbff1b_0
pip                       22.2.2           py37haa95532_0
python                    3.7.13               h6244533_1
setuptools                63.4.1           py37haa95532_0
sqlite                    3.39.3               h2bbff1b_0
vc                        14.2                 h21ff451_1
vs2015_runtime            14.27.29016          h5e58377_2
wheel                     0.37.1             pyhd3eb1b0_0
wincertstore              0.2              py37haa95532_2

Environment info

active environment : test
    active env location : ---\envs\test
            shell level : 2
       user config file : ---\.condarc
 populated config files :
          conda version : 4.12.0
    conda-build version : not installed
         python version : 3.9.12.final.0
       virtual packages : __cuda=11.0=0
                          __win=0=0
                          __archspec=1=x86_64
       base environment : ---  (writable)
      conda av data dir : ---\etc\conda
  conda av metadata url : None
           channel URLs : https://repo.anaconda.com/pkgs/main/win-64
                          https://repo.anaconda.com/pkgs/main/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 : ---\pkgs
                          ---\.conda\pkgs
                          ---\AppData\Local\conda\conda\pkgs
       envs directories : ---\envs
                          ---\.conda\envs
                          ---\AppData\Local\conda\conda\envs
               platform : win-64
             user-agent : conda/4.12.0 requests/2.27.1 CPython/3.9.12 Windows/10 Windows/10.0.19044
          administrator : False
             netrc file : None
           offline mode : False
ocefpaf commented 1 year ago

Looks like a classic case of mixed channels, see https://conda-forge.org/docs/user/tipsandtricks.html#using-multiple-channels

Also, you can try libmamba for a faser solve. See https://github.com/conda-incubator/conda-libmamba-solver#getting-started

Closing this b/c there is nothing we can do here in this feedstock.