TW
just had a `borg check --repair` run and it fixed a ton of issues (replacing missing chunks with all-zero replacement chunks). rc was 0. I was wondering if that is...
Currently, borg has only a few, rather generic return codes: 0 ok, 1 warning, 2 error, >=128 for termination due to signals. This could be improved (preferably with a breaking...
In master branch, mypy is integrated into CI, but most of the code does not have type annotations yet.
https://github.com/Cyan4973/xxHash - not a cryptographic hash fn, not for HMAC! So, maybe we could use it as a crc32 replacement (if we keep the crc32(header+all_data) approach). **borg uses xxh64 at...
try it, test it, document outcome.
master branch: Needs (because openssl is not found via pkg-config): ``` export BORG_OPENSSL_PREFIX=/usr/openssl/1.1 ``` Also, the borgbackup build fails, because it can not find `xxhash.h`, because there is no `(lib)xxh(ash)`...
in borg 1.1, we'll have experimental `borg create --no-cache-sync`, but there is currently no files cache with it. running `borg create` over a bigger amount of files (count as well...
at some places (borg check --repair) we kill repository objects when we encounter IntegrityErrors on them. for many cases this is the right thing to do - if an object...
https://nuitka.net/doc/user-manual.html# can it produce a single-file "exe" now? advantages / disadvantages compared to pyinstaller? Bounty: https://www.bountysource.com/issues/50879646-check-nuitka-again
likely there will be some macFUSE troubles when going to a relatively new macOS version. see there for some notes / insights: https://github.com/borgbackup/borg/pull/6196