desktop-packages team mailing list archive

[Rolf Leggewie <487720@xxxxxxxxxxxxxxxxxx>]

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 Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/487720

Title:
  Restore fails with "Invalid data - SHA1 hash mismatch"

Status in Déjà Dup Backup Tool:
  Invalid
Status in Duplicity - Bandwidth Efficient Encrypted Backup:
  Fix Released
Status in duplicity package in Ubuntu:
  Fix Released
Status in duplicity source package in Lucid:
  Fix Released
Status in duplicity source package in Maverick:
  Won't Fix
Status in duplicity source package in Natty:
  Fix Released

Bug description:
  When restoring a backup, one might see an error like:

  Invalid data - SHA1 hash mismatch:
  Calculated hash: 0b2bc4c2fb98b36f9891f9172f909d70ab5662e9
  Manifest hash: 11cd330357618de52e4e5361a6e63b09ee951ae2

  This can happen when a volume file was not completely written to the
  backend before duplicity was interrupted (say, shutting down the
  machine or whatever).  When duplicity resumes the backup next run, it
  will start with the next volume.  The half-complete volume file will
  sit on the backend and cause this error later when restoring.

  You can manually recover from this by either restoring from your older
  backup sets or by restoring individual files that don't happen to be
  in the corrupted volume.

  == To Reproduce ==

  See attachment
  https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/487720/+attachment/2159465/+files/test.sh
  for a test script tor reproduce the problem.

  == Ubuntu SRU Justification ==

  This is a serious data loss problem for users, which won't be noticed
  until they try to restore.  With Ubuntu 11.10 including Deja Dup, some
  users may think to back up their data first then upgrade, and may
  accidentally create corrupted backups.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/487720/+subscriptions