Maybe you should run duplicity with --verbose and find what's the problematic file from the last path that was printed. The wrong file must be right after the one that triggered the bug.
Maybe you should run duplicity with --verbose and find what's the problematic file from the last path that was printed. The wrong file must be right after the one that triggered the bug.