I have now fixed the bug that I mention above in duplicity trunk, to be released in Duplicity 0.7.08. Can somebody please test with that new version and add a comment as to whether the behaviour above persists?
I have now fixed the bug that I mention above in duplicity trunk, to be released in
Duplicity 0.7.08. Can somebody please test with that new version and add a comment as to whether the behaviour above persists?