*** This bug is a duplicate of bug 1252484 ***
https://bugs.launchpad.net/bugs/1252484
Hi,
I am not sure if this is related, but I am certainly hoping someone can
assist
I'm struggling to restore backups from an older installation of Ubuntu
to a new installation on Ubuntu 16.04. I get the f
*** This bug is a duplicate of bug 1252484 ***
https://bugs.launchpad.net/bugs/1252484
Good news! I've confirmed this is the same underlying issue as bug
1252484 (which I will mark this bug a duplicate of). This is just one of
its symptoms. I've attached the file 'test5.sh' which when run like
I still haven't found the source of this bug. But I have filed a branch
[1] that is basically a glorified version of the patch in comment 6.
This lets the rest of the restore continue when this error happens,
though obviously without the problem file. (It will log an error about
that file, so use
A coworker (Steve Magoun) graciously lent me a backup data set of his
that reproduces this problem.
What appears to have happened on his data set (and presumably others who
are experiencing this) is that a file (say, test.txt) gets backed up in
the initial full backup at time A. This initial back
The link to the source http://atoaudiovisual.com/x/duplicity_joiner.py seems
to be broken
On 6 September 2013 02:18, David Huss 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
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 rece
thx for the patch.. rescued my stuff successfully...
now going for a more robust backup tool :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/662442
Title:
restore fails with "librsync error 103 whi
I have the same problem. I used the patch Christopher Foo provided (many thanks
for that!) - but unfortunately the outcome is the same as what gluca reports.
Would be very grateful for help
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
I have the same problem. The restoration of the home gives the error "librsync
error 103 while in patch cycle".
After applying the pacth, I can restore individual home folder, but not the
entire home, it shows the error AssertionError: first.difftype! = "Diff"
--
You received this bug notificat
Had this happen to me a year ago -- my mistake was failing to test the
restore immediately after the initial backup. I'm using grsync at this
point, a not-great but at least adequate substitute.
On 07/24/2013 12:53 AM, Frederic Dreier wrote:
> I added a try/catch around the faulty lines (like th
I added a try/catch around the faulty lines (like the one in the patch)
and get it going through the restore. just missing sevral files (logs,
gnome config DB, etc.).
I just got a bad feeling about it since my backup is my 'last ressort'
when something goes wrong (here a HD crash). I expect it to
I tried the given patch but it still crash.
Error 'librsync error 103 while in patch cycle' processing
home/john/.eclipse/org.eclipse.platform_3.8_155965261/configuration/org.eclipse.equinox.simpleconfigurator/bundles.info
Traceback (most recent call last):
File "./bin/duplicity", line 1403, in
I have the same problem.
I really need to restore some files from my backup and it is ending with this
error
librsyncError: librsync error 103 while in patch cycle
There is no file in my backup without .gpg
manuall recovery as suggested is causing the same error message.
--
You received this
Constantin, to fix the error you see in your comment #26, delete the
file duplicity-full.20130307T152041Z.vol1001.difftar (note how there is
no .gpg after it). To see instructions for manually recovering, see
https://live.gnome.org/DejaDup/Help/Restore/WorstCase (especially near
the bottom).
--
I tried and never could make it work. Lost a lot of work.
On 06/01/2013 09:41 AM, Constantin Gindele wrote:
> Is there a completely manual way to restore? Removing the encryption
> shouldn't be to hard but it's an incremental backup and I worry about
> stitching the files together.
>
--
You rece
I managed to compile but it still doesn't work. This really unfortunate
since this is my only backup of all documents (well partially that's in
the cloud), photos and music. I updated it before formatting and now I'm
pretty much fucked.
Below's the output.
tantin@Ubook:~/Desktop/duplicity$ sudo
Is there a completely manual way to restore? Removing the encryption
shouldn't be to hard but it's an incremental backup and I worry about
stitching the files together.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Michael, all,
I'm trying to restore one of my backups that DejaDup saved to my NAS. Until now
I have been unsuccessfull in doing so.
My machine is Ubuntu 12.10 and I haven't tried the patching thing yet.
here is the CLI output but I'm happy to dig further upon advice.
$ duplicity --file-to-r
If anyone has a copy of a backup with this bug that they'd be willing to
share, please let me know. We haven't been able to reproduce this error
yet. :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Just to give an update:
I used the patch Chris indicated / attached to manually patch
patchdir.py. I wasn't able to compile Duplicity, but when I tried
restoring my backup again it ran past the error - but I'm experiencing a
different error now (below)!
In terms of Adriano's question asking in w
I also experience this bug. The backups I'm trying to restore are from
my old Ubuntu 13.04 system - but actually one on which I installed the
xubuntu-desktop package on top of - and trying to restore to a new
computer with "plain" Ubuntu 13.04.
I saw a request for logs from before applying the pa
In which directory should i run "patch -p0 <
../duplicity_hax_662442_for_rev884.diff"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/662442
Title:
restore fails with "librsync error 103 while in patc
Thank you for the detailed instructions! I managed to build however I
had to install python-dev and librsync-dev as well two get around the
errors
Python.h: No such file or directory
and
librsync.h: No such file or directory
The commands are
sudo apt-get install python-dev
and
sudo apt-get i
Sorry, I didn't see comment #17. This comment addresses #17 and #18 and
any future readers.
First note, a disclaimer: I am *not* a developer nor maintainer of
duplicity.
Ok, first open up a terminal. It should be in the Accessories menu.
Now type the following and hit enter. Do so for any comman
I second the request on a quick how-to apply the patch for the less
knowledgeable people (like my self) encountering the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/662442
Title:
restore fail
I have run into the same problem trying to restore my backups.
The error I get is -
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1411, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1404, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1338, in mai
Here's a hint at what might be going wrong. While working on the Python
3 port of duplicity, I started getting this error. It turned out to be
because I accidentally closed the patch basis file too soon.
Maybe some code path here is closing a file we need for rsync patching
too early.
--
You r
I'm having the same issue on gentoo
** Changed in: duplicity
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/662442
Title:
restore fails with "librsync error 103 while
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: duplicity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/662442
Title:
r
full file can be found here if patch gets rejected:
http://www.binrand.com/post/4368177-path-index-dan-duplicity.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/662442
Title:
restore fails with "
The attachment "Emergency hax patch that skips the unpatchable file" of
this bug report has been identified as being a patch. The ubuntu-
reviewers team has been subscribed to the bug report so that they can
review the patch. In the event that this is in fact not a patch you can
resolve this situ
** Also affects: duplicity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/662442
Title:
restore fails with "librsync error 103 while in patch cycl
32 matches
Mail list logo
