TW
Considering the linux fat binaries are built on debian, debian 64bit would be a good base. In master branch we use stretch currently. Have a look at the Vagrantfile "stretch64"...
I'ld like to build binaries on machines / OS I control, not in the "cloud".
The stuff needs to be build in the vagrant VM, see Vagrantfile "stretch64" (as I already said above). No travis, no github, no AWS, ... I'ld accept a PR that...
I thought you wanted to make one for the client and one for the server. But just do what makes sense. :) The source dist (sdist, then uploaded to pypi...
See #4538 with some alpine msgpack issue. Guess until that is solved and also borgbackup updated to latest stable, this is no good base.
There's PR #4372 open since quite a while. While I don't personally use docker and thus have no clue about it, I feel it is too complex and should be...
yeah, we can see if we can make some of them more user friendly (and still not losing potentially valuable error information). borg 2.0 will not have any support any...
@rudd-o if you have some time, you could maybe test that, like: - locate some file that has a correct `security.selinux` xattr and not any invalid xattrs - backup that...
Notes: - tests in `borg.testsuite.xattr` work ok on macOS (I also added some with `security.` namespace and didn't spot anything unusual) - the freebsd api for xattrs is a bit...
@rudd-o do you use freebsd? if so, did you restore a linux backup on a freebsd machine?