| see http://lists.nongnu.org/archive/html/duplicity-talk/2016-11/msg00025.html for further discussion, it says that a fix has been committed but i don't think it is a complete fix as obviously this still happens
~Mark
Thank you, Mark! Using only the last digits in the config file let me resume the backup. Mark Grandi <address@hidden> hat am 18. April 2017 um 21:38 geschrieben:
This is a known issue, I think the way to get past it is to change the backup command to just include the last 8 characters of the fingerprint of the key you used, and it should recognize that and work successfully, without requiring you to redo your backup
~Mark
On Apr 18, 2017, at 12:37, Thomas via Duplicity-talk <address@hidden> wrote:
Hi,
Yesterday my backup failed and today I wanted to resume it but I get the error message that it was signed with the key 12456213 instead of 9990006665666999888899912456213 (I changed the numbers).
As you can see the key it tells me is the last part of my actual key.
And idea how I can fix that or do I have to clear everything and start the backup from scratch?
Thanks,
Thomas
_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk
|