TW

Yeah, borg does not solve the problem of deciding whether logical repo contents are like you want them to be. And as soon as you switch off append-only and write...

Just noticed that for repo-monitoring (like listing archives and checking if there are recent backups) a read-only enforcement within borg serve would be also nice to have, so that the...

Crypto: AES-CTR does not have a limited timespan. Why we are doing this is to get rid of the fundamental counter management issues: - you can't lose the local counter...

Repository: It's not just about the "reading PUTs" - it is at quite some places, including borg check (which is already quite complex). I can imagine doing some more and...

Compression: auto mode should go? do we have a ticket about that?

@elho thanks for the detailled feedback btw! This ticket is primarily meant for the to-break-or-not-to-break decision. Once we decide to do a breaking release, requiring new repos, key, export/import, we...

@RonnyPfannschmidt encrypted chunks can be transferred between related repos using the same key material, there is a ticket about that already. I don't know the git pack format, so not...

Note: I updated the topmost post with feedback from you all (thanks!) and also with new insights. I also edited some other posts to remove duplicate / outdated information to...

Progress in #6663 and #6668 looks quite good. About version: if we require people to transfer their repos using `borg transfer`, guess that must be borg 2.0 because you can't...

Well, it's not just like borg needs to get the 64bit time by doing a call, it rather is the whole system of kernel / libc / python needing to...