I have the same issue. I found the same fix as well -- the timeout should be 'None'.
However my case is not about small processors --- I have huge backup set and want to reduce number of duplicity files, so I used a large volsize (--volsize=500).
This is definitely a bug of duplicity. I attached my patch.
I have the same issue. I found the same fix as well -- the timeout should be 'None'.
However my case is not about small processors --- I have huge backup set and want to reduce number of duplicity files, so I used a large volsize (--volsize=500).
This is definitely a bug of duplicity. I attached my patch.