[X] My problem is not solved in the Troubleshooting docs
Anaconda default channels
[X] I do NOT use the Anaconda default channels (pkgs/* etc.)
How did you install Mamba?
Mambaforge or latest Miniforge
Search tried in issue tracker
Potentially linked to #3058
Latest version of Mamba
[X] My problem is not solved with the latest version
Tried in Conda?
I do not have this problem with Conda, just with Mamba
Describe your issue
Hi, this is an issue I first mistakenly opened on the conda-libmamba-solver depository. It's possibly related to #3058, but not sure either.
I installed mamba through mambaforge and use it to build Python virtual environments.I encouter a weird inconsistency when installing packages through mamba depending on the order I provide.
If I do the following :
mamba create -n test s3fs boto3 python=3.11
Mamba ends up installing 48 packages with the following versions :
Now what I don't understand is how such a small change of order can have such a dramatic impact on what gets installed in the end. In particular, the version of s3fs installed in the second configuration is almost 4 years old, whereas it's the latest one in the first configuration.
There seems to be somewhat a conflict of dependencies between s3fs et boto3 because if I create the environment in the second configuration and then runs mamba install s3fs=2024.2.0 in it, I get the following changes :
But in the optimization process that mamba does, I don't understand how a huge major downgrading of s3fs can be prioritized over downgrading boto3 from a few patches, and especially why the result differs so much even when they are simultaneously installed.
The outcome is different when I use conda to create my environment (e.g. conda create -n test s3fs boto3 python=3.11) : it is consistent across orderings in the sense that the same number of packages and versions are installed. However, in both configurations, it installs the version 0.4.2 of s3fs, prioritizing getting the latest of boto3 while accepting a very outdated version for s3fs.
I wonder if it could be related to the fact that s3fs changed their versioning system at some point on conda-forge (see here), going from usual semantic versioning to date-based one. But still the major of the subsequent versions are (way) higher than the previous ones, so I don't see why this should produce this outcome.
Thank's !
mamba info / micromamba info
mamba version : 1.5.7
active environment : test
active env location : /opt/mamba/envs/test
shell level : 2
user config file : /home/onyxia/.condarc
populated config files : /opt/mamba/.condarc
conda version : 24.1.2
conda-build version : not installed
python version : 3.11.6.final.0
solver : libmamba (default)
virtual packages : __archspec=1=skylake_avx512
__conda=24.1.2=0
__glibc=2.35=0
__linux=6.1.0=0
__unix=0=0
base environment : /opt/mamba (writable)
conda av data dir : /opt/mamba/etc/conda
conda av metadata url : None
channel URLs : https://conda.anaconda.org/conda-forge/linux-64
https://conda.anaconda.org/conda-forge/noarch
package cache : /opt/mamba/pkgs
/home/onyxia/.conda/pkgs
envs directories : /opt/mamba/envs
/home/onyxia/.conda/envs
platform : linux-64
user-agent : conda/24.1.2 requests/2.31.0 CPython/3.11.6 Linux/6.1.0-16-amd64 ubuntu/22.04.4 glibc/2.35 solver/libmamba conda-libmamba-solver/23.12.0 libmambapy/1.5.7
UID:GID : 1000:100
netrc file : None
offline mode : False
Troubleshooting docs
Anaconda default channels
How did you install Mamba?
Mambaforge or latest Miniforge
Search tried in issue tracker
Potentially linked to #3058
Latest version of Mamba
Tried in Conda?
I do not have this problem with Conda, just with Mamba
Describe your issue
Hi, this is an issue I first mistakenly opened on the conda-libmamba-solver depository. It's possibly related to #3058, but not sure either.
I installed mamba through mambaforge and use it to build Python virtual environments.I encouter a weird inconsistency when installing packages through mamba depending on the order I provide.
If I do the following :
Mamba ends up installing 48 packages with the following versions :
Now if I just change the order of the packages when installing from :
to :
mamba installs only 37 packages and I get the following versions specs :
Now what I don't understand is how such a small change of order can have such a dramatic impact on what gets installed in the end. In particular, the version of
s3fs
installed in the second configuration is almost 4 years old, whereas it's the latest one in the first configuration.There seems to be somewhat a conflict of dependencies between
s3fs
etboto3
because if I create the environment in the second configuration and then runsmamba install s3fs=2024.2.0
in it, I get the following changes :But in the optimization process that mamba does, I don't understand how a huge major downgrading of
s3fs
can be prioritized over downgradingboto3
from a few patches, and especially why the result differs so much even when they are simultaneously installed.The outcome is different when I use
conda
to create my environment (e.g.conda create -n test s3fs boto3 python=3.11
) : it is consistent across orderings in the sense that the same number of packages and versions are installed. However, in both configurations, it installs the version0.4.2
ofs3fs
, prioritizing getting the latest ofboto3
while accepting a very outdated version fors3fs.
I wonder if it could be related to the fact that
s3fs
changed their versioning system at some point onconda-forge
(see here), going from usual semantic versioning to date-based one. But still the major of the subsequent versions are (way) higher than the previous ones, so I don't see why this should produce this outcome.Thank's !
mamba info / micromamba info
Logs
No response
environment.yml
No response
~/.condarc
No response