Comment 1 for bug 662442

I'm also getting this while doing a "duplicity restore --no-encryption". The specific error I see is "python: ERROR: (rs_file_copy_cb) unexpected eof on fd8". This is duplicity 0.6.13.

In my case, one of the incremental backups might have been truncated/interrupted as there were occasional read-errors on the source system in question. However, as this disk has now completely died and this backup is the only one, I'd like to hear if there is any way at all to make duplicity recover from this "unexpected end of input" and continue with the restore operation?