duplicity-team team mailing list archive

[edso <question246088@xxxxxxxxxxxxxxxxxxxxx>]

Question #246088 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/246088

    Status: Open => Answered

edso proposed the following answer:
On 26.03.2014 16:16, Ted wrote:
> New question #246088 on Duplicity:
> https://answers.launchpad.net/duplicity/+question/246088
> 
> I'm trying to restore a file that appears in the list when I run list-collection-status, but every time I attempt to restore it, I get the message:
> 
> <file> not found in archive, no files restored.
> 
> Duplicity was crashing on .21, so I upgraded to the last stable version in the PPA, and now I get this message: 
> 
> 
> python2.7: ERROR: (rs_file_copy_cb) unexpected eof on fd94
> python2.7: ERROR: (rs_job_complete) patch job failed: unexpected end of input
> Error 'librsync error 103 while in patch cycle' patching .
> 
> Is this the cause for the file being unrestorable? Is there any way to mitigate this? I upgraded to trunk after reading the bug report related to this error message, but that bug report said the data loss error was fixed in trunk.
> 
> Is it possible that duplicity is erroneously reporting the file's presence in the archive? The file is a gpg public keyring, and it's continually refreshed by parcimonie, so it's possible that there's no good backup if the file was changed while a backup was running, correct?
> 

try to restore an older state (backup).

the initial error was fixed yes, but erroneous backups like your's will
stay of cause as they are.

..ede/duply.net

-- 
You received this question notification because you are a member of
duplicity-team, which is an answer contact for Duplicity.