TW
Thanks for the hint, I removed the documentation label.
Maybe this can be solved by some docs: - the passphrase can be put in a env var, so it won't ask - using --repository-only and --archives-only one can split...
The problem with asking for the passphrase (and setting up the `key` object) early is that we need a valid chunk for this. The current code just uses the first...
For well-working repos, it could be done early (and maybe the passphrase just written into process env internally). For damaged repos (or lost chunks cache), we first need to do...
Sorry, not familiar with packaging for unraid, but maybe @dmacias72 or some other unraid user can help with that.
Well, just try it out? I don't think I want to make the 1.1-maint branch docs more complicated by making them python version specific. For master, we require python >=...
Quote from the parse_intermixed_args docs: """These parsers do not support all the argparse features, and will raise exceptions if unsupported features are used. In particular, subparsers, argparse.REMAINDER, and mutually exclusive...
Side note: `bento/freebsd-11.4` (amd64) boots successfully.
well, the most obvious and pressing use case is not having the backups erased by an attacker who has broken into your production system (backup client) and knows how to...
`borgbackup` currently uses `python-llfuse` (which is unmaintained and uses libfuse 2). The successor project `pyfuse3` requires libfuse3. So, to keep `borg` running on macOS, we'll need libfuse3 api at some...