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 default, but turning it off is
a simple check when starting your backup for the first time. It seems
sensible if you already trust the destination and are using https or ssh
or some such.
I also found other corruption issues that are not specific to no-
encryption mode, addressed in the linked branch above.
** Changed in: duplicity (Ubuntu)
Importance: Undecided => Critical
** Changed in: duplicity (Ubuntu)
Status: New => Triaged
** Changed in: duplicity (Ubuntu)
Assignee: (unassigned) => Michael Terry (mterry)
** Also affects: duplicity (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: duplicity (Ubuntu Quantal)
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1091269/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
