I'm having the same problem from time to time:
Local and Remote metadata are synchronized, no sync needed.
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1377, in ?
with_tempdir(main)
File "/usr/bin/duplicity", line 1370, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1250, in main
globals.archive_dir).set_values()
File "/usr/lib64/python2.4/site-packages/duplicity/collections.py", line 694,
in set_values
(backup_chains, self.orphaned_backup_sets,
File "/usr/lib64/python2.4/site-packages/duplicity/collections.py", line 819,
in get_backup_chains
map(add_to_sets, filename_list)
File "/usr/lib64/python2.4/site-packages/duplicity/collections.py", line 809,
in add_to_sets
if set.add_filename(filename):
File "/usr/lib64/python2.4/site-packages/duplicity/collections.py", line 93,
in add_filename
self.set_manifest(filename)
File "/usr/lib64/python2.4/site-packages/duplicity/collections.py", line 123,
in set_manifest
assert not self.remote_manifest_name, (self.remote_manifest_name,
AssertionError:
('duplicity-inc.20120507T053251Z.to.20120509T042329Z.manifest.part',
'duplicity-inc.20120507T053251Z.to.20120509T042329Z.manifest.gpg')
Removing the file in question on the remote side usually fixes it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/633101
Title:
Duplicity is failing with an assertion error when looking for a non-
existent manifest file
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/633101/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
