Open vickorian opened 1 year ago
After some testing it's one of the following packages causing the error.
colorama=0.4.6=pypi_0 ffmpeg-python=0.2.0=pypi_0 filelock=3.8.0=pypi_0 future=0.18.2=pypi_0 huggingface-hub=0.10.1=pypi_0 idna=3.4=py39haa95532_0 more-itertools=9.0.0=pypi_0 packaging=21.3=pypi_0 pyparsing=3.0.9=pypi_0 pyyaml=6.0=pypi_0 regex=2022.9.13=pypi_0 tokenizers=0.13.1=pypi_0 tqdm=4.64.1=pypi_0 transformers=4.23.1=pypi_0
ffmpeg-python=0.2.0=pypi_0
more-itertools=9.0.0=pypi_0
pyyaml=6.0=pypi_0
regex=2022.9.13=pypi_0
There is a conflict in one of these four.
I can confirm that these PermissionErrors
still exist in the latest conda version 23.1.0
running on windows 10 22H2.
In my case it failed to patch the prefix of a .pyd
file of wrapt
in the site packages folder of the environment I tried to unpack. The issue is also reproducible (with the same file being affected) on dedicated windows CI nodes that do not use any "file monitoring" solutions, which is usually a good candidate for these kinds of problems.
What @vickorian and I have in common is that we try to use conda-unpack.exe
. So I tried the documented alternative conda-unpack-script.py
with the interpeter that is part of the env I'm trying to unpack. Same problem. Then I used the script but with an independent python interpreter - and it worked reliably.
The conda-unpack.exe
uses the interpreter that is part of the environment to be patched. In other words, the environment is used to patch itself. Maybe that is just a bad idea in general and the robust way is to always use an independent interpreter to perform this job.
$ conda info
active environment : base
active env location : C:\workflow2\msys2\opt\workflow\workflow_conda_scientific_env_1.6.0.0
shell level : 1
user config file : C:\Users\john\.condarc
populated config files : C:\workflow2\msys2\opt\workflow\workflow_conda_scientific_env_1.6.0.0\.condarc
C:\Users\john\.condarc
conda version : 23.1.0
conda-build version : not installed
python version : 3.9.16.final.0
virtual packages : __archspec=1=x86_64
__cuda=11.7=0
__win=0=0
base environment : C:\workflow2\msys2\opt\workflow\workflow_conda_scientific_env_1.6.0.0 (writable)
conda av data dir : C:\workflow2\msys2\opt\workflow\workflow_conda_scientific_env_1.6.0.0\etc\conda
conda av metadata url : None
channel URLs : https://artifactory.intra.somecorp.com/artifactory/api/conda/conda-anaconda-pkgs-main-virtual/win-64
https://artifactory.intra.somecorp.com/artifactory/api/conda/conda-anaconda-pkgs-main-virtual/noarch
https://artifactory.intra.somecorp.com/artifactory/api/conda/conda-anaconda-pkgs-msys2-virtual/win-64
https://artifactory.intra.somecorp.com/artifactory/api/conda/conda-anaconda-pkgs-msys2-virtual/noarch
https://artifactory.intra.somecorp.com/artifactory/api/conda/conda-anaconda-pkgs-r-virtual/win-64
https://artifactory.intra.somecorp.com/artifactory/api/conda/conda-anaconda-pkgs-r-virtual/noarch
package cache : C:\workflow2\msys2\opt\workflow\workflow_conda_scientific_env_1.6.0.0\pkgs
envs directories : C:\Users\john\AppData\Local\conda\conda\envs
C:\workflow2\msys2\opt\workflow
C:\workflow2\msys2\opt\workflow\workflow_conda_scientific_env_1.6.0.0\envs
C:\Users\john\.conda\envs
platform : win-64
user-agent : conda/23.1.0 requests/2.28.1 CPython/3.9.16 Windows/10 Windows/10.0.19045
administrator : False
netrc file : None
offline mode : False
@axel-kah your solution works.
Use the interpreter of base environment to run the <env name>/Script/conda-unpack-script.py
script.
Thanks.
I also second @ZhiZe-ZG's comment.
Specifically, running python <env name>/Scripts/conda-unpack-script.py
as described in the directory above the environment name. Running python Scripts/conda-unpack-script.py
from within the environment folder still resulted in permission errors.
Checklist
What happened?
I'm moving an env in an attempt to create an offline system backup or system transfer. Issue is occurring when trying to transfer it to a test unit. Please see the attached screenshot.
Conda Info
Conda Config
Conda list
Additional Context
No response