TW
Found something: https://github.com/python/cpython/blob/3.9/Lib/tarfile.py#L1176 That tarfile code expects: - keys to be str and encodable to utf-8 - values to be str and encodable to utf-8 or using "surrogateescape"
xattrs are done, #8467. ACLs still todo.
https://man.archlinux.org/man/tar.5.en there is some docs about `SCHILY.acl.access` and also other, platform specific formats.
Code in #8856 now correctly supports access and default ACLs (like seen on Linux). Can somebody practically test this? Note: now in master branch, will be also in 2.0.0b20.
Maybe rather work: - as a user (not root) - in a python virtual env See top of the page there: https://nsupdateinfo.readthedocs.io/en/latest/admin.html#administrating-the-service Also, guess using git master branch would be...
Related: - #7374 - #6019 - #4498 (also a lot of details / discussion why borg 1.2+ works fd-based, benchmarks)
With default borg options, it can not be sped up while retaining its consistency properties, because even with a files cache hit (== no need to read the file's content),...
Looks like the test code expects a warning rc (rc == 1), but gets success (rc == 0). Guess the warning was because of how moin 1.x represents hardlinks in...
Just wanted to add here why for the migration from borg 1.x to borg 2 we did not choose the tar format to copy archives from old to new repos:...