Backup failed with an unknown error (line 1414, with_tempdir)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
New
|
Undecided
|
Unassigned | ||
deja-dup (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
When running with "DEJA_DUP_DEBUG=1 deja-dup --backup", the backup terminates with the following:
DUPLICITY: INFO 1
DUPLICITY: . retrieving file duplicity-
DUPLICITY: INFO 1
DUPLICITY: . making GET request to https:/
DUPLICITY: INFO 1
DUPLICITY: . completed request with status 200 OK
DUPLICITY: INFO 1
DUPLICITY: . Making directory /home/simon-
DUPLICITY: DEBUG 1
DUPLICITY: . Removing still remembered temporary file /var/tmp/
DUPLICITY: DEBUG 1
DUPLICITY: . Removing still remembered temporary file /var/tmp/
DUPLICITY: ERROR 30 AssertionError
DUPLICITY: . Traceback (most recent call last):
DUPLICITY: . File "/usr/bin/
DUPLICITY: . with_tempdir(main)
DUPLICITY: . File "/usr/bin/
DUPLICITY: . fn()
DUPLICITY: . File "/usr/bin/
DUPLICITY: . restore(col_stats)
DUPLICITY: . File "/usr/bin/
DUPLICITY: . restore_
DUPLICITY: . File "/usr/lib/
DUPLICITY: . for ropath in rop_iter:
DUPLICITY: . File "/usr/lib/
DUPLICITY: . final_ropath = patch_seq2ropath( normalize_ps( patch_seq ) )
DUPLICITY: . File "/usr/lib/
DUPLICITY: . assert first.difftype != "diff", patch_seq
DUPLICITY: . AssertionError: [(('README',) reg), (('README',) reg), (('README',) reg), (('README',) reg)]
DUPLICITY: .
System information:
Ubuntu 13.10
deja-dup:
Installed: 27.3.1-0ubuntu1
Candidate: 27.3.1-0ubuntu1
Version table:
*** 27.3.1-0ubuntu1 0
500 http://
100 /var/lib/
duplicity:
Installed: 0.6.21-0ubuntu4.1
Candidate: 0.6.21-0ubuntu4.1
Version table:
*** 0.6.21-0ubuntu4.1 0
500 http://
100 /var/lib/
0.
500 http://
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: deja-dup 27.3.1-0ubuntu1
ProcVersionSign
Uname: Linux 3.11.0-
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: i386
Date: Mon Dec 23 20:56:29 2013
MarkForUpload: True
SourcePackage: deja-dup
UpgradeStatus: Upgraded to saucy on 2013-12-21 (2 days ago)
Status changed to 'Confirmed' because the bug affects multiple users.