Restore fails assertion on "len( patch_seq ) == 1"

[Rainer Rohde]

Backup fails to verify the files backed up to my external USB3 drive. Here's the output from the GUI:

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1411, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1404, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1338, in main
    restore(col_stats)
  File "/usr/bin/duplicity", line 632, in restore
    restore_get_patched_rop_iter(col_stats)):
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 526, in Write_ROPaths
    for ropath in rop_iter:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 499, in integrate_patch_iters
    final_ropath = patch_seq2ropath( normalize_ps( patch_seq ) )
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 466, in patch_seq2ropath
    assert len( patch_seq ) == 1, len( patch_seq )
AssertionError: 4

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: deja-dup 25.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-8.17-generic 3.8.0
Uname: Linux 3.8.0-8-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
Date: Thu Mar 14 17:03:18 2013
EcryptfsInUse: Yes
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: deja-dup
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Steve Magoun (smagoun)]

This is a regression from 12.10. I reliably get this error when backing up to my external disk on 13.04.

[Michael Terry (mterry)]

Based on bug 1025718, I'm going to mark this as an actual bug in duplicity, not in how deja-dup drives it.

[Michael Terry (mterry)]

This *might* be related to bug 720525. Same function.

[Kenneth Loafman (kenneth-loafman)]

I will look into this. I think you are correct.

On Thu, May 16, 2013 at 2:34 PM, Michael Terry
<email address hidden>wrote:

> This *might* be related to bug 720525. Same function.
>
> --
> You received this bug notification because you are subscribed to
> Duplicity.
> https://bugs.launchpad.net/bugs/1155345
>
> Title:
> Restore fails assertion on "len( patch_seq ) == 1"
>
> Status in Duplicity - Bandwidth Efficient Encrypted Backup:
> New
> Status in “duplicity” package in Ubuntu:
> Confirmed
>
> Bug description:
> Backup fails to verify the files backed up to my external USB3 drive.
> Here's the output from the GUI:
>
> Traceback (most recent call last):
> File "/usr/bin/duplicity", line 1411, in <module>
> with_tempdir(main)
> File "/usr/bin/duplicity", line 1404, in with_tempdir
> fn()
> File "/usr/bin/duplicity", line 1338, in main
> restore(col_stats)
> File "/usr/bin/duplicity", line 632, in restore
> restore_get_patched_rop_iter(col_stats)):
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 526, in Write_ROPaths
> for ropath in rop_iter:
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 499, in integrate_patch_iters
> final_ropath = patch_seq2ropath( normalize_ps( patch_seq ) )
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 466, in patch_seq2ropath
> assert len( patch_seq ) == 1, len( patch_seq )
> AssertionError: 4
>
> ProblemType: Bug
> DistroRelease: Ubuntu 13.04
> Package: deja-dup 25.5-0ubuntu1
> ProcVersionSignature: Ubuntu 3.8.0-8.17-generic 3.8.0
> Uname: Linux 3.8.0-8-generic x86_64
> NonfreeKernelModules: nvidia
> ApportVersion: 2.9.1-0ubuntu1
> Architecture: amd64
> Date: Thu Mar 14 17:03:18 2013
> EcryptfsInUse: Yes
> MarkForUpload: True
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: deja-dup
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/duplicity/+bug/1155345/+subscriptions
>

[Michael Terry (mterry)]

Good news! I've confirmed this is the same underlying issue as bug 1252484 (which I will mark this bug a duplicate of). This is just one of its symptoms. I've attached the file 'test3.sh' which when run like 'sh test3.sh' should reliably reproduce this exception.

This bug has been fixed in duplicity trunk (and Ubuntu 13.10+). The fix will be in the upcoming duplicity 0.6.23 release.

I've prepared fixes for older Ubuntu releases, but the updates need testers before they can be released to everyone. If you are an Ubuntu user of an older release, please go to bug 1252484 and follow the instructions for testing the update. Thanks!