Strange! I found a workaround which irritates me.
I moved all previous backups to a different location. Next backup starts with a full backup which -> WORKS I do a differential backup immediately afterwards -> WORKS I move the old backups into place again and gain access to my old backup and the new differentials work. Unfortunately deja-dup does not make a full backup on demand. One has to trick it into doing it (or wait for the mechanism to kick in) Now to the irritation: Why does the differential work now and did not work before? There is no indication as to the backup forward-chaining encryption (It uses gpg - well actually duplicity does). So how can the SHA1 checksums differ? For this bug: It could be closed as far as I am concerned but the issue requires further investigation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1424164 Title: Deja-dup backup failed with SHA1 mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1424164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
