Julien Jerphanion
Julien Jerphanion
Hi, I cannot reproduce the error with micromamba 1.5.10 and micromamba 2.0 using: ``` micromamba install xmlschema==2.5.0=pyhd8ed1ab_0 -y ``` I also cannot reproduce the error with mamba 1.5.10 and mamba...
This might be due to the usage of `libarchive` from Anaconda's default channels. We recommend against using them because they are incompatible with conda-forge's.
For all Semantic Versioned packages, I would recommend solving environments and pinning the min version (included) as the current minor number and the max version as the next major (excluded)...
mamba could support `uv` conditionally if it is installed, yes. Pull requests are welcome. 🙂
[`mamba-org/boa`](https://github.com/mamba-org/boa) has been archived, we recommend using [`rattler-build`](https://github.com/prefix-dev/rattler-build) now.
I cannot reproduce the error when installing `numpy-2.1.1-py312h58c1407_0.conda` (from `conda-forge`) when placed on `/tmp` using: ```bash micromamba install --yes --name grid file:///tmp/linux-64/numpy-2.1.1-py312h58c1407_0.conda ``` In the example you gave, @msmitherdc, it...
Can you provide a reproducer for this issue (by providing such a conda package)?
Thank you, @chrisburr. I currently cannot reproduce the issue with your instance.
I can now reproduce with and without a docker container. It fails on my machine with: ``` error libmamba Cannot find a valid extracted directory cache for 'snakemake-7.32.4-hdfd78af_1.tar.bz2' ```
I cannot reproduce the problem as of 503f0aa9b0fbf1442e5adca8e6152ad7f13b5a8e.