Environment creation fails with relative path

[Hind-M]

Reported in micromamba-releases:

Running micromamba create and pointing the prefix to a relative path fails in error when the input file contains a pip section. This behavior occurs on both windows and linux.

micromamba env create --yes -f deps.yaml -p folder/subfolder

critical libmamba Cannot activate, prefix does not exist at: 'folder/subfolder'
/tmp/mambafKZrZk11KQo: line 5: folder/subfolder/bin/python: No such file or directory
critical libmamba pip failed to install packages

[Hind-M]

@amgcc Can you please specify the micromamba version you're using? Thanks!

[jjerphan]

I cannot reproduce the error as of 2.0.

[jjerphan]

Can you provide a reproducer, @amgcc? Thank you.

[amgcc]

I was testing this with micromamba 1.5.8, I will retest on 2.0 next week.

[amgcc]

With a toy example, I too am unable to reproduce on linux. Please close the issue for now, thanks.

[amgcc]

Ok, I was able to finally reproduce this but having trouble producing an example. The error occurs if providing a relative prefix where the parent folder does not exist. I think part of my issue is that I was relying on mamba to create my exported environment (lock) files because of an issue with pip. Now that micromamba has since fixed the issue, this other issue is probably no longer possible. I will reopen a ticket if I can reproduce failure on micromamba 2.

micromamba env create --yes -f env_pip.yaml -p missing_folder worked
micromamba env create --yes -f env_pip.yaml -p missing_folder/subdir failed

[amgcc]

I created a new ticket for a related issue around relative paths causing console scripts to fail to create correctly here with detailed reproduction steps.

[Klaim]

I can´t reproduce this with 2.0.5.rc0 neither on Windows nor Linux. Could you check with that version?

[jjerphan]

I also cannot reproduce the issue on Linux with 2.0.5.