witten closed issue witten/borgmatic#73

17 hours ago

witten commented on issue witten/borgmatic#73

Well, I went ahead and implemented this. Just released as part of borgmatic 1.2.8. Give it a shot and let me know how it works out for you!

17 hours ago

witten pushed tag 1.2.8 to witten/borgmatic

17 hours ago

witten commented on issue witten/borgmatic#86

Mentioned another implementation idea for this ticket in comments on #97. Basically, the "gimme the last successful backup" feature *could* be in a separate piped command that specializes in dealing with and parsing Borg JSON output. Example:

17 hours ago

witten commented on issue witten/borgmatic#97

Also, not necessarily a deal-breaker for the never-capture-Borg-output approach, but implementing #86 would *probably* require post-processing Borg JSON output in some way.. That is, unless it's implemented as a separate tool that's designed for post-processing direct Borg output, e.g.:

17 hours ago

witten commented on issue witten/borgmatic#97

If I recall correctly, the main reason for capturing Borg's JSON output and putting it in a JSON list is for the (fairly common) case of multiple repositories in a borgmatic configuration file or multiple separate borgmatic configuration files. The idea is that in a single borgmatic run, borgmatic may be invoking `borg --json` multiple times, and therefore need to gather the results into a common JSON list for ease of parsing by any downstream consumers of borgmatic output.

18 hours ago

witten commented on issue witten/borgmatic#73

Okay, then what I'm thinking is the adding support for the following to the consistency section of the config file:

1 day ago

witten commented on issue witten/borgmatic#101

Glad to hear that upgrading Borg cleared that up. For what it's worth, I've just set up a few more end-to-end tests in continuous integration to catch this sort of issue in the future. I've also mentioned a minimum Borg version in the README. Thanks for reporting the issue!

1 day ago

witten commented on issue witten/borgmatic#101

Got it. Thanks for the clarification. Borg version 1.0.11 is pretty old at this point. Have you tried upgrading? I can try to reproduce this later on, but it may be worth trying Borg 1.1.7 or thereabouts, if possible, to see if that fixes this. They may have changed their `--info` sub-command semantics.

2 days ago

witten commented on issue witten/borgmatic#101

Have you generated a borgmatic configuration with `generate-borgmatic-configuration` as per the README? Without a configuration file, `borgmatic --info` won't know what repository to operate on.

2 days ago

witten commented on issue witten/borgmatic#100

I was indeed a little worried about the logging fixes changing the user experience for certain use cases. Looks like that's happened here!

4 days ago