BUG: mamba update --file does not take into account file changes

[h-vetinari]

Troubleshooting docs

• My problem is not solved in the Troubleshooting docs

Anaconda default channels

• I do NOT use the Anaconda default channels (pkgs/* etc.)

How did you install Mamba?

Mambaforge or latest Miniforge

Search tried in issue tracker

update, --file, -f, environment.yml etc.

Latest version of Mamba

• My problem is not solved with the latest version

Tried in Conda?

Not applicable

Describe your issue

conda-smithy has an environment.yml file which specifies the dependencies necessary for the development of smithy.

Recent changes (conda-forge/conda-smithy@86ffbd9 & conda-forge/conda-smithy@814ffed) added new dependencies to that file, but when I do

mamba update --file environment.yml

to update my existing environment (that had been created in the past), after updating my local checkout to upstream main (conda-forge/conda-smithy@814ffed), those new dependencies (py-rattler, etc.) end up not getting installed.

There is no error in the logs, so the fact that the installation of mamba update --file environment.yml succeeds without matching the specification in that file is very misleading. After running this command, the environment needs to match the constraints in the file (ideally), or a clear error needs to be raised if that's not possible for some reason.

mamba info / micromamba info

>mamba info

       libmamba version : 2.5.0
          mamba version : 2.5.0
           curl version : libcurl/8.18.0 Schannel zlib/1.3.1 libssh2/1.11.1 WinLDAP
     libarchive version : libarchive 3.8.5 zlib/1.3.1 liblzma/5.8.2 bz2lib/1.0.8 liblz4/1.10.0 libzstd/1.5.7 libxml2/2.d
       envs directories : E:\miniforge\envs
          package cache : E:\miniforge\pkgs
                          C:\Users\[...]\.mamba\pkgs
                          C:\Users\[...]\AppData\Roaming\.mamba\pkgs
            environment : smithy-dev (active)
           env location : E:\miniforge\envs\smithy-dev
      user config files : C:\Users\[...]\.mambarc
 populated config files : C:\Users\[...]\.condarc
                          E:\miniforge\.condarc
       virtual packages : __win=10.0.26100=0
                          __archspec=1=x86_64_v3
               channels : https://conda.anaconda.org/conda-forge/noarch
                          https://conda.anaconda.org/conda-forge/win-64
       base environment : E:\miniforge
               platform : win-64

Logs

environment.yml

~/.condarc

[h-vetinari]

As it turns out, one of the recent additions (conda-forge-tick) is not available on windows due to a transitive dependency; however, even if I remove that from environment.yml, mamba update ... still does not update the environment, nor does it error.