aawsome

A simple workaround for this bug is: use an empty destination dir to restore to.

Thanks a lot for this question! I'd also like to keep this issue as a tracking issue and close it when I think we are ready for production. So far,...

The two restic-compatibility-issues are IMO fixed by #116 which has just been merged.

Seems like `actions-rs/audit-check@v1` doesn't support adding custom args, unfortunately. I suggest waiting for chrono 0.4.20

Now chrono 0.4.20 is out. But `cargo audit` still claims the dependency on `time` which doesn't seem to be removed. So, we wait a bit more for what's happening... BTW:...

Thanks for the question! Its zstd and allows currently between 0 (no compression) and 22. If not set (and repo version is 2 which is standard), the zstd standard compression...

Thanks for the question! Actually I didn't dive into zstd and just read somewhere that only the positve levels should be exposed to users. But yes, negative values also work,...

Ah, and to set negative compressions, you have to use `rustic-rs config --set-compression=-4` instead of `rustic-rs config --set-compression -4` (the latter bails that the option `-4` is not supported).

Actually this result is not completely unexpected: The time added by higher compression is probably more than saved due to the lower size to save in the backend. In fact,...

Actually I cannot judge if this is worthwhile enhancement. Can anyone help test this with different repo sizes and give some feedback about the results?