Jonas Haag
Jonas Haag
Can you please show the list of packages in that env? Also this is a very old version of Mamba, consider upgrading.
Could it be that some of the packages are not available for Python 3.7? Or maybe there is another conflict? Unfortunately Mamba's (and Conda's) conflict reporting aren't very good yet....
Seems like there is a conflict with some other package in your other env. Unfortunately I don't have good recommendations other than trying to remove some packages from that env...
Not sure what went wrong but can you try `mamba install -n base 'conda>=22'`?
Note that you should not mix `conda-forge` and `defaults` (`pkgs/...`). Actually we recommend to not use `pkgs/...`.
I think Mamba isn't available in the Anaconda channels so it doesn't find any updates. Or maybe you need to specify `'conda>=22' 'mamba>=0.27'` explicitly? Using conda-forge and Anaconda channels together...
There are no changes to published tarballs. You're just not guaranteed that `micro.mamba.pm/api/micromamba/` will always return the same tarball (it actually redirects to the latest build I guess).
Well you'll always want to use the latest build. I don't know if micro.mamba.pm supports specifying a build number. Although that would open another problem of knowing what's the latest...
How are you folks keeping up to date with the latest versions? Just asking because you should also be looking for new builds of the same version, not just new...
Not sure if it’s related but you should not install anything into the base env.