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

Operation not permitted while trying hard linking #516

bb-migration opened this Issue Mar 14, 2016 · 3 comments


None yet
3 participants

bb-migration commented Mar 14, 2016

Originally reported by: sorin (Bitbucket: sorin, GitHub: sorin)

It seems that even current versions of setuptools to fail ugly when cannot be performed, and this seems to be something more and more common, especially due to the virtualisation.

Hard links are not supported in many network mounts and virtual environments. In my case I am using Parallels to share my home directory which also contains the python modules which I am developing, allowing me to run the same code on OS X, Ubuntu and Windows.

It seems that doing python sdist fails with the (in)famous error:

hard linking README.txt -> foo-0.1
error: Operation not permitted

Based on the thread from I tried to add del to my and it started to work.

While this workaround seems ugly, it seems that's the only one that covers all failure cases.

Problem reproduces with both 5.5.x and 20.x versions of setuptools.


This comment has been minimized.


jamadden commented Jul 21, 2016

I just got bit by this using setuptools-24.2.1. I was trying to use docker to produce gevent manylinux wheels in a more automated fashion using a mount point from the host machine (OS X).

The del workaround fixed my problem.


This comment has been minimized.


jaraco commented Jul 21, 2016

This issue exists in Python (in distutils.command.sdist.sdist.make_release_tree and distutils.file_util.copy_file), but it could be patched here.

@jaraco jaraco closed this in 9f77a06 Jul 21, 2016


This comment has been minimized.


jaraco commented Jul 21, 2016

Release pending with v24.3.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment