TW
@m3nu @witten @sophie-h
@m3nu Thanks for the feedback! Just as a general note: support for these error/warning codes could be added at any time IF the wrapper checks/sets BORG_EXIT_CODES and reacts accordingly. This...
@witten Thanks for the feedback. Just be careful: setting that will only change behaviour for borg >= 1.4.
@LocutusOfBorg @FelixSchwarz @bket ^^^
BTW, a nice side-effect of this would be that our `setup*.py` code could be reduced / simplified significantly (compare master to current 1.4-maint).
Thanks for the feedback. Guess I'll wait a while if somebody wants to hold me back and if not: remove the bundled stuff, simplify setup*.py (in 1.4-maint). For a while,...
Fixed by #8117.
borg backup archives always are **full backups of all the files in your backup source** (the paths you give to borg, minus the excludes you specify) as they were present...
If you want to have a merge operation, I suggest you plan how that would work and open a new ticket or PR with your proposal - just a hint...
Check the docs about `--lock-wait`: https://borgbackup.readthedocs.io/en/stable/usage/general.html The default wait time is rather short (1s). If you run multiple borg client against the same repo, a much longer wait time can...