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 section, modified it to use
verify instead of the check kludge, and have been unable to reproduce it
after many runs.  It still fails to verify this bug.

There are multiple options both stable and latest:
- Stable snap builds - “sudo snap install duplicity —classic"
- Latest snap builds - “sudo snap install duplicity —classic —edge"
- Stable pip3 builds - “sudo pip3 install duplicity"
- Latest pip3 builds - “sudo pip3 install --pre duplicity"
- Stable duplicity PPA - 
https://code.launchpad.net/~duplicity-team/+archive/ubuntu/duplicity-release-git
- Latest duplicity PPA - 
https://code.launchpad.net/~duplicity-team/+archive/ubuntu/duplicity-develop-git
- Stable tarball install - https://launchpad.net/duplicity/+download
- Source - https://gitlab.com/duplicity/duplicity

Note 1: UNINSTALL duplicity first if it was installed from a different
source..  This is due to divergent install locations, especially between
repository installs and the other forms.

Note 2: Launchpad PPAs contain builds for Bionic 18.04, Eoan 19.10,
Focal 20.04,  Hirsute 20.10 and Impish 21.04.

Note 3: Xenial 16.04 works with Snap and Pip installs, but cannot be
built under Launchpad PPAs at the moment.

** Changed in: duplicity
       Status: Confirmed => Incomplete

-- 
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:
https://bugs.launchpad.net/deja-dup/+bug/487720/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to