TW
borg2: we can now have multiple "related" repos based on the same key material. this includes the key for the id hash / MAC and also the chunker secret, thus...
scope of this ticket =============== let's concentrate here on the issue of csize (and also size) information in the items' chunks lists, in the chunks and files cache. no crypto...
we have argon2 kdf now, is there any reason to keep pbkdf2 for keys of new repos? borg 2.0 still needs to support such keys to read old repos, but...
I started some experimental multithreading code there: https://github.com/thomaswaldmann/borg/tree/multithreading especially: https://github.com/ThomasWaldmann/borg/commit/240a27a22774eb055c7bff5097b4d6557bbb81c5 From Python c-api docs: "the standard zlib and hashlib modules release the GIL when compressing or hashing data." So current...
the code could be reviewed whether this distinction is cleanly handled everywhere. `borg create` has some switches like `--noacls`, `--noxattrs`, `--nobsdflags`, `--noatime` that can be used to not store such...
there is a known issue that if a file somehow fails in the middle of processing (e.g. due to an I/O error within the input file), borg will have written...
Some hints for Linux / BSD / other OS package maintainers: ## libs additionally to openssl, libacl, libattr, lz4 and zstd, we now also need: - libxxhash some of that...
if a repo only has PUT2 (and no PUT any more), e.g. `replay_segments` should call `iter_objects(..., read_data=False)`. with PUT tags, a CRC32 check was only possible when reading the data...
we don't have that yet, but guess it would be good for: - decompression buffer allocation - not only knowing the csize, but also the size without actually reading and...