I have adapted the patch from
https://bugs.launchpad.net/duplicity/+bug/1702696 to skip faulty tar
files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/487720
Title:
Restore fails with "Invalid
Please upgrade to the current version of duplicity. If you can reliably
reproduce this bug, please let me know what you did, in detail, with
attached -v9 log files and minimal munging. DO NOT copy/paste log files
here. They are impossible to read.
I took the script in the bug description
I need to find a reproducible scenario.
There are hardware reasons for network transfers to drop bits and there
are software reasons for the problem. I think we are seeing a mix of
both. I've had downloads fail when going through a non-parity checking
router, so that's one for hardware. I've
Still a problem in Ubuntu 20.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/487720
Title:
Restore fails with "Invalid data - SHA1 hash mismatch"
To manage notifications about this bug go to:
This is absolutely still an issue in the latest versions of Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/487720
Title:
Restore fails with "Invalid data - SHA1 hash mismatch"
To manage
maverick has seen the end of its life and is no longer receiving any
updates. Marking the maverick task for this ticket as Won't Fix.
** Changed in: duplicity (Ubuntu Maverick)
Status: Fix Committed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
I have the same problem.
Invalid data - SHA1 hash mismatch for file:
duplicity-inc.20140424T053227Z.to.20140508T021212Z.vol51.difftar.gz
Calculated hash: e28fd59e70f82bb126eb76b0c76b807cc03f5b27
Manifest hash: 38e4dd60b6aac680493f03d8c8a3145474d45907
I could not fall back to a previous backup
I also have this bug agean:
Invalid data - SHA1 hash mismatch for file:
duplicity-inc.2006T102651Z.to.20111213T090632Z.vol9.difftar.gz
Calculated hash: 4bdbd1f52c07593da62c276e0aa343d8ff3b555f
Manifest hash: 5d9e6492392576d22baf0eeac67d88e04cf23495
I am using Ubuntu 11.10 64 bit with Deja
Please open a new question for your issue. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/487720
Title:
Restore fails with Invalid data - SHA1 hash mismatch
To manage notifications about
I ran into the same problem. duplicity version 0.6.15 (might have been 0.6.14
when doing the backup).
I used backintime for years until december 2011, found deja dup, and deleted
the plain backup after a successful backup with deja dup.
What a mistake.
After an update the system broke and was
hello, i have an old corrupted backup and i decided to restore
everything i can into a separate folder. I ran: duplicity restore
file:///path/to/backup /target/folder and the restore began. After a
while it failed with the following message:
Invalid data - SHA1 hash mismatch for file:
I thought I'd write a little HOWTO on recovering from this bug, in case
people hit it from using versions that aren't fixed. It won't be able
to restore all original files, but you can restore most.
The central issue is that one or several of the backup volumes will be
corrupted and likely not
** Tags added: verification-done-natty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/487720
Title:
Restore fails with Invalid data - SHA1 hash mismatch
To manage notifications about this bug go
This bug was fixed in the package duplicity - 0.6.08b-0ubuntu2.1
---
duplicity (0.6.08b-0ubuntu2.1) lucid-proposed; urgency=low
* debian/patches/04dontrestoresameblock.dpatch:
- Fix possible backup corruption bug when resuming backups
LP: #613244
*
** Tags removed: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/487720
Title:
Restore fails with Invalid data - SHA1 hash mismatch
To manage notifications about this bug go to:
This bug was fixed in the package duplicity - 0.6.13-0ubuntu1.1
---
duplicity (0.6.13-0ubuntu1.1) natty-proposed; urgency=low
* debian/patches/06shamismatch.dpatch:
- Fix possible backup corruption bug when resuming backups
LP: #487720
-- Michael Terry mte...@ubuntu.com
I have tested duplicity from Natty Proposed Repository and it did fix
the bug. Works fine.
I ran:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/487720/+attachment/2159465/+files/test.sh
and got the message: Yay! We didn't hit the bug!
Before the upgrade of duplicity from the
Hi everybody, I'm setting the bug back to verification-needed .. while
it was verified on lucid, it also needs to be independently verified on
maverick and natty still.
** Tags removed: verification-done
** Tags added: verification-done-lucid verification-needed
--
You received this bug
@Clint: I added back v-done. If a bug has both -needed and -done, it'll
appear in purple on sru-report. That means ubuntu-sru has to manually
check which releases can go to -updates and which not, but that way we
avoid blocking on e. g. maverick verification for the lucid update.
** Tags added:
Hello Michael Terry
I ran your test in my lucid system after enabling duplicity-proposed and
found no errors. I still have Lucid's Duplicity with no PPA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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/bugs/487720
Title:
Restore fails with Invalid data - SHA1 hash mismatch
To manage
Hello Andrew, or anyone else affected,
Accepted duplicity into natty-proposed, the package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in
** Branch linked: lp:ubuntu/lucid-proposed/duplicity
** Branch linked: lp:ubuntu/maverick-proposed/duplicity
** Branch linked: lp:ubuntu/natty-proposed/duplicity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm going to prepare an SRU for Ubuntu for this, since it can silently
corrupt your backup. I'll update the description shortly with SRU
justifications. Ken, hope you don't mind the noise, it just made sense
for me to use the same bug since all the history is here.
** Also affects: duplicity
** Description changed:
- I'm trying to restore a large directory. Twice now, the restore has
- failed at the same point about a third of the way through. Here's the
- error:
+ When restoring a backup, one might see an error like:
Invalid data - SHA1 hash mismatch:
Calculated hash:
** Changed in: duplicity (Ubuntu Lucid)
Status: New = Confirmed
** Changed in: duplicity (Ubuntu Maverick)
Status: New = Confirmed
** Changed in: duplicity (Ubuntu Natty)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I've uploaded packages for lucid, maverick, and natty to -proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/487720
Title:
Restore fails with Invalid data - SHA1 hash mismatch
To manage
27 matches
Mail list logo
