-
Notifications
You must be signed in to change notification settings - Fork 353
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mamba/mambaforge/miniconda run into errors with ncurse package on win10 WSL #1144
Comments
#1143 might fix the mambaforge issue. |
I am having the exact same problem with the miniforge installer and this completely prevents installation under Win10 WSL2. What appears to happen is that after unpacking ncurses it warns about the checksum being wrong for some files that were overwritten because of name clashes caused by Win file system not being cases sensitive. It then seems to delete the folder into which ncurses was unpacked under ..../pkgs/ and then naturally fails to find the folder and crashes with error mentioned above. |
@bioXiaoheng @cvjjm could you retry with the latest miniforge release? |
The error is now different but installation still fails under WSL2 during the ncurses step:
|
And indeed the two files it complains about do exist and one is a broken link:
|
Here's what I see with an |
Is this still an issue? |
Hi Mamba developers,
I'm suggested to open this recent issue with conda-forge (conda-forge/miniforge#205) here because micromamba and mamba have the same issue with some files in the ncurse package when operating on windows 10 WSL (Ubuntu 20.04).
In particular, I was trying to install mambaforge using the shell script
Mambaforge-Linux-x86_64.sh
on my WSL (windows 10 home version 10.0.19043 build 19043, WSL v 10.0.19041.1151, Ubuntu version 2004.2021.222.0) to set up snakemake and run into the errors below:Later, I was able to install miniconda3 using the script
Miniconda3-py38_4.9.2-Linux-x86_64.sh
and install mambaforge with the conda commandconda install mamba -n base -c conda-forge
.As I followed through the snakemake tutorial, a similar warning/error appeared when running the command
mamba env create --name snakemake-tutorial --file environment.yaml
:Despite the two errors though, this command was still able to complete itself, and the command
conda activate snakemake-tutorial
still works.Attached are the two files (in tar.gz) mentioned by both. I'm wondering 1) why these errors occur, and more importantly 2) will they (or the mechanism that caused them) bring future problems as I keep using mamba and snakemake on my WSL?
eterm_files.tar.gz
The text was updated successfully, but these errors were encountered: