AssertionError: assert len(chain_list) == 2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
Medium
|
Unassigned | ||
Déjà Dup |
Invalid
|
High
|
Unassigned |
Bug Description
Bug present in both duplicity 0.6.11 on Ubuntu Maverick 10.10 (from PPA), and the standard shipping Maverick duplicity, which was used to create the backup.
Python 2.6.6. Target file system is a godaddy Linux virtual server.
Unfortunately I don't have the error output of the actual full backup created by the standard Maverick version of duplicity. It appeared to backup all files, and then fail at the very end (sadly, after 2 days continual operation and 32 GB of data).
When running duplicity --encrypt-key 29435027 --sign-key 29435027 --ssh-options=
I get this crash:
Traceback (most recent call last):
File "/usr/bin/
with_
File "/usr/bin/
fn()
File "/usr/bin/
globals.
File "/usr/lib/
backup_chains)
File "/usr/lib/
sig_chains = sig_chains and self.get_
File "/usr/lib/
assert len(chain_list) == 2
AssertionError
Related branches
- duplicity-team: Pending requested
-
Diff: 129 lines (+29/-18)1 file modifiedduplicity-bin (+29/-18)
summary: |
- failure in assert statement in collections.py + AssertionError: assert len(chain_list) == 2 |
Changed in deja-dup: | |
importance: | Undecided → Critical |
status: | New → Confirmed |
importance: | Critical → High |
Changed in duplicity: | |
importance: | Undecided → Medium |
milestone: | none → 0.6.15 |
status: | New → Fix Committed |
Changed in deja-dup: | |
status: | Confirmed → Invalid |
Changed in duplicity: | |
status: | Fix Committed → Fix Released |
I get the same output when attempting to restore from a backup using Deja-Dup 16.1.1. Restore fails with an unknown error followed by the above.