TW
@rrueger sorry for late answer. Yes, you can directly go from 1.1.18 to 1.2.7/1.2.8 or even 1.4.x, but follow the upgrade steps detailed in the changelog.
This issue was just closed there due to merging https://github.com/xstatic-py/xstatic/pull/14 into master branch. It would be good if master branch of `xstatic` code gets some practical testing before a 2.0.0...
what error do you get in such a case?
Well, finding that repo issue was in a rather slow operation (syncing the local chunks index by processing all archives' metadata).
Even when comparing to `borg check --archives-only ...`?
Guess there can't be a fast check if a repo is ok. Maybe best is to run an automated borg check periodically e.g. Sunday night.
"currently active" refers to a `borg create` run, processing one recursion root after the other... IIRC, they can come from commandline args as well as from `R` lines in the...
@cloudrac3r good catch! this is the place to fix it - do you want to make a pull request (against 1.1-maint and master)? https://github.com/borgbackup/borg/blob/1.1.10/src/borg/archiver.py#L2231 (the docs, man pages, etc. will...
@achikin that is what `borg create --list --dry-run ...` is intended for.
@miguno Good idea - do you want to make a pull request against master and 1.1-maint?