# CondaPkg error

**URL:** <https://discourse.julialang.org/t/condapkg-error/100523>\
**Category:** General Usage\
**Tags:** question, error, pythoncall, conda\
**Created:** [June 18, 2023, 4:41pm UTC](https://discourse.julialang.org/t/condapkg-error/100523 "2023-06-18T16:41:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![e3c6](https://avatars.discourse-cdn.com/v4/letter/e/e79b87/32.png) [@e3c6](https://discourse.julialang.org/u/e3c6)\
**Post date:** [June 18, 2023, 4:41pm UTC](https://discourse.julialang.org/t/condapkg-error/100523/1 "2023-06-18T16:41:53Z")

</div>

I’ve been getting errors like this lately, from `CondaPkg`:

> critical libmamba filesystem error: cannot copy symlink: Operation not permitted [~/.julia/scratchspaces/0b3b1443-0f03-428d-bdfb-f27f9c1191ea/root/pkgs/libstdcxx-ng-12.3.0-h0f45ef3\_0/lib/libstdc++.so] [~/some\_project/.CondaPkg/env/lib/libstdc++.so]

Any idea where this could come from?

This is happening when pre-compiling a package that uses `PythonCall` and `CondaPkg`. I can post a full stack-trace if people thing it can be useful.

---

<div class="post-metadata">

**Author:** ![ufechner7](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ufechner7/32/51363_2.png) [@ufechner7](https://discourse.julialang.org/u/ufechner7)\
**Post date:** [June 18, 2023, 4:49pm UTC](https://discourse.julialang.org/t/condapkg-error/100523/2 "2023-06-18T16:49:54Z")

</div>

What is your operating system? Does deleting the scratchspace and trying again help? Do you have sufficient free disk space? Which file system do you use?

---

<div class="post-metadata">

**Author:** ![e3c6](https://avatars.discourse-cdn.com/v4/letter/e/e79b87/32.png) [@e3c6](https://discourse.julialang.org/u/e3c6)\
**Post date:** [June 18, 2023, 5:59pm UTC](https://discourse.julialang.org/t/condapkg-error/100523/3 "2023-06-18T17:59:31Z")

</div>

OS: Linux (WSL on Windows 11)  
Sufficient disk space: Yes  
Filesystem: NTFS

I will try deleting the scratch-space and report here.  
But the issue is that this error has been popping up frequently, in different systems. So there could be some bug that is corrupting something.