TW
About the log you posted: That seems to be a `Cython` issue, somehow borg does not detect Cython is installed (could be because Cython is not working / is not...
The root cause might be this line failing in setup.py: ``` from Cython.Build import cythonize ``` Can you invoke a python interpreter with your virtual env active and try that?...
> And yet same error. It comes from the [setup.py line 83](https://github.com/borgbackup/borg/blob/0c1df415d74ebb11f5e738cf7b0aae7a45967f07/setup.py#L83) If you use the 1.2.8 checkout, better use the 1.2.8 tag to link to source files, like: https://github.com/borgbackup/borg/blob/1.2.8/setup.py...
Can you try whether up/downgrading setuptools/pip/wheel helps (inside the venv)?
Good catch! Is there a traceback for this ImportError? Also: can this "failed to map" error msg be seen if you remove the try/except in borg's setup.py?
I am working on an improvement, PR will come soon, would be good if you can try it out. Can you try #8210? It is for 1.4-maint branch, but guess...
Add "bug" label because borg's `setup.py` has hidden the original exception message, making it hard to find the root cause of this problem.
OK, I'll add a hint about +exec.
OK, as far as borg is concerned, I'll close this - it now gives a helpful error message. The root cause of this is the noexec fs and that the...
Usually that works, borg internally detects the name by which it was invoked and then behaves differently. Try: - the single file fat binary - the directory based fat binary...