I get this occasionally over an SFTP interface to a remote block storage
system from time-to-time. Due to their implementation there is an
occasional and variable but short delay in newly written files becoming
accessible in subsequent requests. As its a question of timing it
usually doesn't cause a problem, but sometimes it does and then
duplicity is unable to perform subsequent backups without manually
wiping the local cache.

Note the first run terminated with the error `Giving up after 1
attempts. IOError: [Errno 2] No such file`. Followed by the assertion
errors described above for all subsequent runs until the cache is
cleared.

We may take the view that it is reasonable for the program to give up
when during the original error on the remote, but I think it should to
handle corruption in its own cache without manual intervention.

-- 
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

Reply via email to