[Duplicity-talk] Duplicity bug report: duplicity crashes if the GPG key is not trusted

[Maurizio Vitale]

I don't seem to be getting the registration confirmation from  
Savannah, hence cannot properly report bugs.
Hope mailing here works as a temporary substitute.

I'm trying to simulate what happens when the backed up machine fails  
and you need to start the backup process from
another machine. Normally you would import the (carefully saved) GPG  
secret key and use it to restore from your backup.

After that you're on a new machine and you can start backing up  
again. You can generate a new GPG key or you may want
to keep using the old one. If you chose to use the old one you have  
to remember to do gpg --edit-key <KEY ID> and
trust the key.

Failure to do so result in duplicity crashing with a stack trace. The  
log explains what happens, but it would be nice if
duplicity exited with a nice error message instead.

Regards,

        Maurizio

Maurizio Vitale

Polymath Solutions
309 Denniston Ave
Pittsburgh, PA 15206

T +1.412.453.5606
M address@hidden
W www.polymath-solutions.com