Comment 3 for bug 713832

After reencrypting the complaining duplicity volume and verifying that it no longer produced a gpg decription failure, I proceeded to re-attempt the duplicity restore.

But unfortunately, since gpg includes a seed which results in a different hash anytime an encryptis performed, the manifest hash and calculated hash differ resulting in yet another failure (at exactly the same volume and file).