Launchpad has imported 13 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=922576.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://hel
This bug was fixed in the package duplicity - 0.6.08b-0ubuntu2.2
---
duplicity (0.6.08b-0ubuntu2.2) lucid-proposed; urgency=low
* debian/patches/07volcorruption.dpatch:
- Fix some data-corruption issues when resuming an interrupted
backup (LP: #1091269)
-- Michael Terry
Not gauche at all. Much better to verify your own SRUs than to leave
them unloved!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091269
Title:
Data corruption when resuming
To manage notifications
I know it's gauche to verify your own SRU, but since no one else was
doing it... I tested on lucid and verified the fix.
** Tags removed: removal-candidate verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
** Branch linked: lp:ubuntu/precise-proposed/duplicity
** Branch linked: lp:~ubuntu-branches/ubuntu/quantal/duplicity/quantal-
proposed
** Branch linked: lp:ubuntu/raring/duplicity
** Branch linked: lp:ubuntu/raring-proposed/duplicity
--
You received this bug notification because you are a mem
** Branch linked: lp:ubuntu/duplicity
** Branch linked: lp:ubuntu/lucid-proposed/duplicity
** Branch linked: lp:~ubuntu-branches/ubuntu/oneiric/duplicity/oneiric-
proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
** Changed in: duplicity (Ubuntu Oneiric)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091269
Title:
Data corruption when resuming
To manage notification
** Bug watch added: Red Hat Bugzilla #922576
https://bugzilla.redhat.com/show_bug.cgi?id=922576
** Also affects: duplicity (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=922576
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a m
Hello Pascual, or anyone else affected,
Accepted duplicity into lucid-proposed. The package will build now and
be available at http://launchpad.net/ubuntu/+source/duplicity/0.6.08b-
0ubuntu2.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
h
** Changed in: duplicity
Status: Fix Committed => Fix Released
** Changed in: duplicity
Milestone: None => 0.6.21
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091269
Title:
Data corrup
duplicity (0.6.19-0ubuntu2.2) quantal-proposed; urgency=low
* debian/patches/09volcorruption.dpatch:
- Backport a fix for a restart test that caused FTBFS on armhf
-- Michael Terry Fri, 11 Jan 2013 13:59:19 -0500
duplicity (0.6.19-0ubuntu2.1) quantal-proposed; urgency=low
[ Michael T
This bug was fixed in the package duplicity - 0.6.18-0ubuntu3.1
---
duplicity (0.6.18-0ubuntu3.1) precise-proposed; urgency=low
[ Chris J Arges ]
* debian/patches/07caching.dpatch:
- Backport caching work done by Steve Atwell. (LP: #1013446)
[ Michael Terry ]
* debian/pat
I forgot to mention that I was testing on Precise, duplicity version
0.6.18-0ubuntu3.1
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
The proposed package fixes the data corruption issue.
I ran the test script with the version in the normal repository first and got
corruption for the first run. I updated to the proposed package and ran the
test script several times and there was no corruption at all. Thank you for the
fix!
--
Hello Pascual, or anyone else affected,
Accepted duplicity into precise-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/duplicity/0.6.18-0ubuntu3.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
h
Hello Pascual, or anyone else affected,
Accepted duplicity into quantal-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/duplicity/0.6.19-0ubuntu2.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
h
Here's a test script, run like so to test the system duplicity:
sudo /bin/bash ./auto-ctrl-c-test.sh -s
** Attachment added: "auto-ctrl-c-test.sh"
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1091269/+attachment/3479775/+files/auto-ctrl-c-test.sh
** Description changed:
[Impact
** Changed in: duplicity
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091269
Title:
Data corruption when resuming
To manage notifications about this bug go
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: duplicity (Ubuntu Quantal)
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/1091269
T
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: duplicity (Ubuntu Precise)
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/1091269
T
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: duplicity (Ubuntu Oneiric)
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/1091269
T
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: duplicity (Ubuntu Lucid)
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/1091269
Tit
** Also affects: duplicity (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: duplicity (Ubuntu Oneiric)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
This bug was fixed in the package duplicity - 0.6.20-0ubuntu4
---
duplicity (0.6.20-0ubuntu4) raring; urgency=low
* debian/patches/08volcorruption.dpatch:
- Fix some data-corruption issues when resuming an interrupted
backup (LP: #1091269)
-- Michael TerryMon, 07 Jan
** Description changed:
+ [Impact]
+ It's very easy to accidentally corrupt the backup copy of a file when
resuming an interrupted backup.
+
+ Specifically, there are several ways to end up backing up corrupted
+ data:
+
+ A) If resuming after a volume that ended in a one-block file, we would s
** Summary changed:
- Data corruption when resuming with --no-encryption option
+ Data corruption when resuming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091269
Title:
Data corruption when res
** Branch linked: lp:~mterry/duplicity/static-corruption
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091269
Title:
Data corruption when resuming with --no-encryption option
To manage notificatio
Oh sorry, didn't see your comment. get_footer() seems to be some a
function to add padding to a tar block. Not sure how important it is,
since we seem to be doing fine without it.
As for how common no-encryption is, I'm confident it's relatively common
among Deja Dup users. Encryption is the de
See https://code.launchpad.net/~mterry/duplicity/static-
corruption/+merge/142044 for some work on corruption issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091269
Title:
Data corruption whe
Not a clue. What's get_footer()? We did not encounter this problem
because duplicity has not been used much in no-encryption mode before now.
I'm still unclear why anyone would want to do so. Kind of like using a
wrench to drive in a nail.
On Sat, Jan 5, 2013 at 10:35 AM, Michael Terry
wrote:
It looks like all the files that have problems are files split across
volumes. So I posit that since the amount to read from the input files
is based on how close the gzipped volume is to our target size (see
GzipWriteFile()), that amount to read could be different if the gzip
compression is diffe
I don't understand why this patch would fix the bug. It looks like it
just means that we always call next() with exactly 128*1024, whereas
before this patch, we might call it with anything from 32*1024 to
128*1024.
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
The attachment "no-encryption-corruption-fix.patch" 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
situation by removing
** 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/1091269
Title:
Data corruption when resuming with --no-encryption option
34 matches
Mail list logo
