ede

the options "should" work over all backends, but sure there might be implementation flaws. if so please open a ticket on https://gitlab.com/duplicity/duplicity/-/issues/ and let's fix it :) apart from the repo i only offer snapshots on https://duply.net/Code#Latest_Development_Snapshot if some issue needs double checking by the issuer. currently there not much developing on duply as it is quite mature and stable fortunately.

the options "should" work over all backends, but sure there might be implementation flaws. if so please open a ticket on https://gitlab.com/duplicity/duplicity/-/issues/ and let's fix it :) apart from the repo i only offer snapshots on https://duply.net/Code#Latest_Development_Snapshot if some issue needs double checking by the issuer. currently there not much developing on duply as it is quite matrue and stable fortunately.

Add a retry mechanism in case of duplicity backend error

hey @3rjpq0d6x, duply is mainly meant to be run manually or by cron and be finished after it is done. i'm unsure if it is a good idea to have it sleeping and retry blindly if some error occurs. duplicity itself already has a retry mechanism build in that should be of help to you. look at the man page https://duplicity.us/stable/duplicity.1.html for the options --num-retries --backend-retry-delay does that help? ..sunny regards ede

release 2.5.6

conf setting "--exclude-other-filesystems" corrupts generated cmd line

released as v2.5.6 . THANKS again David!

release 2.5.6