Skip to content
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

critical libmamba permissions: The system cannot find the path specified.: "testenv\Scripts\pip.exe" #2546

Closed
2 tasks done
cjdoris opened this issue May 26, 2023 · 3 comments · Fixed by #2612
Closed
2 tasks done

Comments

@cjdoris
Copy link

cjdoris commented May 26, 2023

Troubleshooting docs

  • My problem is not solved in the Troubleshooting docs

How did you install Mamba?

Micromamba

Search tried in issue tracker

critical libmamba permissions: The system cannot find the path specified

Latest version of Mamba

  • My problem is not solved with the latest version

Tried in Conda?

I didn't try

Describe your issue

This command:

micromamba create -y -p ./testenv -c conda-forge pip

produces this error:

error    libmamba Error opening for writing "testenv\\Scripts\\pip-script.py": No such file or directory
error    libmamba Error opening for writing "testenv\\Scripts\\pip.exe": No such file or directory
critical libmamba permissions: The system cannot find the path specified.: "testenv\Scripts\pip.exe"

It appears to only occur with micromamba v1.4.3 (the latest version on conda-forge) on Windows.

I have observed it locally, in CI and I've had a couple of bug reports with the same issue on a package of mine which depends on micromamba.

mamba info / micromamba info

__
          __  ______ ___  ____ _____ ___  / /_  ____ _
         / / / / __ `__ \/ __ `/ __ `__ \/ __ \/ __ `/
        / /_/ / / / / / / /_/ / / / / / / /_/ / /_/ /
       / .___/_/ /_/ /_/\__,_/_/ /_/ /_/_.___/\__,_/
      /_/


            environment : None (not found)
           env location : -
      user config files : C:\Users\chris\.mambarc
 populated config files :
       libmamba version : 1.4.3
     micromamba version : 1.4.3
           curl version : libcurl/7.86.0-DEV Schannel zlib/1.2.13
     libarchive version : libarchive 3.6.1 zlib/1.2.13 liblzma/5.4.0 bz2lib/1.0.8 libzstd/1.5.2
       virtual packages : __win=0=0
                          __archspec=1=x86_64
                          __cuda=10.1=0
               channels :
       base environment : C:\Users\chris\AppData\Local\micromamba\root
               platform : win-64

Logs

__
          __  ______ ___  ____ _____ ___  / /_  ____ _
         / / / / __ `__ \/ __ `/ __ `__ \/ __ \/ __ `/
        / /_/ / / / / / / /_/ / / / / / / /_/ / /_/ /
       / .___/_/ /_/ /_/\__,_/_/ /_/ /_/_.___/\__,_/
      /_/

conda-forge/win-64                                          Using cache
conda-forge/noarch                                          Using cache

Transaction

  Prefix: testenv

  Updating specs:

   - pip


  Package                 Version  Build               Channel           Size
-------------------------------------------------------------------------------
  Install:
-------------------------------------------------------------------------------

  + bzip2                   1.0.8  h8ffe710_4          conda-forge     Cached
  + ca-certificates      2023.5.7  h56e8100_0          conda-forge     Cached
  + libexpat                2.5.0  h63175ca_1          conda-forge     Cached
  + libffi                  3.4.2  h8ffe710_5          conda-forge     Cached
  + libsqlite              3.42.0  hcfcfb64_0          conda-forge     Cached
  + libzlib                1.2.13  hcfcfb64_4          conda-forge     Cached
  + openssl                 3.1.0  hcfcfb64_3          conda-forge     Cached
  + pip                    23.1.2  pyhd8ed1ab_0        conda-forge     Cached
  + python                 3.11.3  h2628c8c_0_cpython  conda-forge     Cached
  + setuptools             67.7.2  pyhd8ed1ab_0        conda-forge     Cached
  + tk                     8.6.12  h8ffe710_0          conda-forge     Cached
  + tzdata                  2023c  h71feb2d_0          conda-forge     Cached
  + ucrt             10.0.22621.0  h57928b3_0          conda-forge     Cached
  + vc                       14.3  hb25d44b_16         conda-forge     Cached
  + vc14_runtime      14.34.31931  h5081d32_16         conda-forge     Cached
  + vs2015_runtime    14.34.31931  hed1258a_16         conda-forge     Cached
  + wheel                  0.40.0  pyhd8ed1ab_0        conda-forge     Cached
  + xz                      5.2.6  h8d14728_0          conda-forge     Cached

  Summary:

  Install: 18 packages

  Total download: 0 B

-------------------------------------------------------------------------------



Transaction starting
Linking libexpat-2.5.0-h63175ca_1
Linking ucrt-10.0.22621.0-h57928b3_0
Linking ca-certificates-2023.5.7-h56e8100_0
Linking vc14_runtime-14.34.31931-h5081d32_16
Linking vc-14.3-hb25d44b_16
Linking vs2015_runtime-14.34.31931-hed1258a_16
Linking libsqlite-3.42.0-hcfcfb64_0
Linking openssl-3.1.0-hcfcfb64_3
Linking libffi-3.4.2-h8ffe710_5
Linking bzip2-1.0.8-h8ffe710_4
Linking xz-5.2.6-h8d14728_0
Linking tk-8.6.12-h8ffe710_0
Linking libzlib-1.2.13-hcfcfb64_4
Linking tzdata-2023c-h71feb2d_0
Linking pip-23.1.2-pyhd8ed1ab_0
error    libmamba Error opening for writing "testenv\\Scripts\\pip-script.py": No such file or directory
error    libmamba Error opening for writing "testenv\\Scripts\\pip.exe": No such file or directory
critical libmamba permissions: The system cannot find the path specified.: "testenv\Scripts\pip.exe"

environment.yml

No response

~/.condarc

No response

@kariharju
Copy link

Hi, getting this as well.

  • Started when updated micromamba from v1.4.2 to v1.4.3 (also reproduces on v1.4.4)
  • Works on Linux, fails on Windows

@jonashaag
Copy link
Contributor

Is this the same as #2609?

@wolfv
Copy link
Member

wolfv commented Jun 21, 2023

Yes, this is very likely the same bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants