Message when not able to solve for package does not make sense

[DManowitz]

Troubleshooting docs

• My problem is not solved in the Troubleshooting docs

How did you install Mamba?

Other (please describe)

Search tried in issue tracker

None found

Latest version of Mamba

• My problem is not solved with the latest version

Tried in Conda?

Not applicable

Describe your issue

I tried to install a package and mamba was not able to solve to install it. However, the informational message displayed does not actually indicate why it could not solve:

Could not solve for environment specs
The following package could not be installed
└─ folium 0.13.0**  is requested and can be installed.

It would seem from this message that the package should be installable.

mamba info / micromamba info

__    __    __    __
                 /  \  /  \  /  \  /  \
                /    \/    \/    \/    \
███████████████/  /██/  /██/  /██/  /████████████████████████
              /  / \   / \   / \   / \  \____
             /  /   \_/   \_/   \_/   \    o \__,
            / _/                       \_____/  `
            |/
        ███╗   ███╗ █████╗ ███╗   ███╗██████╗  █████╗
        ████╗ ████║██╔══██╗████╗ ████║██╔══██╗██╔══██╗
        ██╔████╔██║███████║██╔████╔██║██████╔╝███████║
        ██║╚██╔╝██║██╔══██║██║╚██╔╝██║██╔══██╗██╔══██║
        ██║ ╚═╝ ██║██║  ██║██║ ╚═╝ ██║██████╔╝██║  ██║
        ╚═╝     ╚═╝╚═╝  ╚═╝╚═╝     ╚═╝╚═════╝ ╚═╝  ╚═╝

        mamba (1.4.2) supported by @QuantStack

        GitHub:  https://github.com/mamba-org/mamba
        Twitter: https://twitter.com/QuantStack

█████████████████████████████████████████████████████████████


     active environment : py38_ml_TfGpuMain
    active env location : C:\Users\manow\miniconda3\envs\py38_ml_TfGpuMain
            shell level : 1
       user config file : C:\Users\manow\.condarc
 populated config files : C:\Users\manow\.condarc
          conda version : 4.14.0
    conda-build version : not installed
         python version : 3.9.16.final.0
       virtual packages : __cuda=12.1=0
                          __win=0=0
                          __archspec=1=x86_64
       base environment : C:\Users\manow\miniconda3  (writable)
      conda av data dir : C:\Users\manow\miniconda3\etc\conda
  conda av metadata url : None
           channel URLs : https://conda.anaconda.org/pytorch/win-64
                          https://conda.anaconda.org/pytorch/noarch
                          https://conda.anaconda.org/pyg/win-64
                          https://conda.anaconda.org/pyg/noarch
                          https://conda.anaconda.org/nvidia/label/cuda-11.3.1/win-64
                          https://conda.anaconda.org/nvidia/label/cuda-11.3.1/noarch
                          https://conda.anaconda.org/conda-forge/win-64
                          https://conda.anaconda.org/conda-forge/noarch
                          https://conda.anaconda.org/intel/win-64
                          https://conda.anaconda.org/intel/noarch
                          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 : C:\Users\manow\miniconda3\pkgs
                          C:\Users\manow\.conda\pkgs
                          C:\Users\manow\AppData\Local\conda\conda\pkgs
       envs directories : C:\Users\manow\miniconda3\envs
                          C:\Users\manow\.conda\envs
                          C:\Users\manow\AppData\Local\conda\conda\envs
               platform : win-64
             user-agent : conda/4.14.0 requests/2.28.1 CPython/3.9.16 Windows/10 Windows/10.0.19045
          administrator : False
             netrc file : None
           offline mode : False

Logs

Contact me if you need this.  Github wouldn't let me post the verbose logs, as it complained about it being too long.

environment.yml

No response

~/.condarc

pip_interop_enabled: true
channel_priority: disabled
channels:
  - pytorch
  - pyg
  - nvidia/label/cuda-11.3.1
  - conda-forge
  - intel
  - defaults

[fperez]

Same here - I have an environment where something is preventing me from upgrading JuptyerLab to 4.0, and I'm getting that exact same, non-sensical message:

Looking for: ['jupyterlab==4.0.2']

conda-forge/osx-arm64                                       Using cache
conda-forge/noarch                                          Using cache
pkgs/main/noarch                                              No change
pkgs/main/osx-arm64                                           No change
pkgs/r/noarch                                                 No change
pkgs/r/osx-arm64                                              No change

Pinned packages:
  - python 3.10.*

Could not solve for environment specs
The following package could not be installed
└─ jupyterlab 4.0.2  is requested and can be installed.

Obviously there's something wrong with the message, since it's saying something contradictory.

More importantly, mamba should show why it can't install a requested package/update. Right now, debugging this is a painful trial-and-error process of removing packages one (or a few) at a time until stumbling on the offending one. With a big environment, this can take hours.

Thanks for any tips on how to resolve this - it's a complete blocker for using mamba in many scenarios, unfortunately.

[AntoinePrv]

Thanks for the feedback. Closing this as we are tracking it in #2543 (edit #2078). We will schedule some time to look into it.

[fperez]

@AntoinePrv - did you have a typo in your message above? You indicate it's being tracked elsewhere, but you pointed to this same issue :)

[AntoinePrv]

Yes, sorry for the typo, I fixed it.