The link to the source http://atoaudiovisual.com/x/duplicity_joiner.py seems to be broken
On 6 September 2013 02:18, David Huss <da...@huss.at> wrote: > For those who still want (or have to) to restore their backups by hand, I > found a solution for me. > The unpack-part is easy, the stich/join-part is not. So I wrote an > application for that. More details here: > http://blog.atoaudiovisual.com/2013/09/restore-broken-deja-dup-backup-hand/ > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/662442 > > Title: > restore fails with "librsync error 103 while in patch cycle" > > To manage notifications about this bug go to: > https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions > -- Martin -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with "librsync error 103 while in patch cycle" Status in Duplicity - Bandwidth Efficient Encrypted Backup: Confirmed Status in “duplicity” package in Ubuntu: Confirmed Bug description: I'm doing a trial restore from an sftp backup, and it fails like so: Writing .bazaar/plugins/svn/backup.bzr/repository/packs/5e32df252c6c9b80b70d63cab2a52f1a.pack of type reg Deleting /tmp/duplicity-4I6eKU-tempdir/mktemp-B5f55D-4 Processed volume 2 of 2531 Running 'sftp -oServerAliveInterval=15 -oServerAliveCountMax=2 mbp@grace' (attempt #1) sftp command: 'get "/backup/lithe/home_mbp.duplicity//duplicity-inc.20100210T222519Z.to.20100429T235919Z.vol2.difftar.gz" "/tmp/duplicity-4I6eKU-tempdir/mktemp-7d1sNq-22"' Writing .bazaar/plugins/svn/backup.bzr/repository/upload of type dir ...... Writing .byobu/status of type reg Writing .byobu/windows of type reg python: ERROR: (rs_file_copy_cb) unexpected eof on fd23 python: ERROR: (rs_job_complete) patch job failed: unexpected end of input Traceback (most recent call last): File "/home/mbp/work/duplicity/duplicity-bin", line 1245, in <module> with_tempdir(main) File "/home/mbp/work/duplicity/duplicity-bin", line 1238, in with_tempdir fn() File "/home/mbp/work/duplicity/duplicity-bin", line 1192, in main restore(col_stats) File "/home/mbp/work/duplicity/duplicity-bin", line 539, in restore restore_get_patched_rop_iter(col_stats)): File "/home/mbp/work/duplicity/duplicity/patchdir.py", line 520, in Write_ROPaths for ropath in rop_iter: File "/home/mbp/work/duplicity/duplicity/patchdir.py", line 493, in integrate_patch_iters final_ropath = patch_seq2ropath( normalize_ps( patch_seq ) ) File "/home/mbp/work/duplicity/duplicity/patchdir.py", line 473, in patch_seq2ropath misc.copyfileobj( current_file, tempfp ) File "/home/mbp/work/duplicity/duplicity/misc.py", line 166, in copyfileobj buf = infp.read(blocksize) File "/home/mbp/work/duplicity/duplicity/librsync.py", line 80, in read self._add_to_outbuf_once() File "/home/mbp/work/duplicity/duplicity/librsync.py", line 94, in _add_to_outbuf_once raise librsyncError(str(e)) librsyncError: librsync error 103 while in patch cycle ~/work/duplicity/duplicity-bin -v7 --no-encrypt restore ~/tmp/grace- restore 30.59s user 5.18s system 49% cpu 1:11.81 total Using the tip of the 0.6 branch on Ubuntu Maverick. I think I've seen this once before too. The 'unexpected eof' error suggests that one of the increment files could be truncated, but that doesn't seem likely: I haven't had any filesystem problems, and at the gzip level all of them seem to be ok. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
