Update of bug #20234 (project duplicity):
Status: In Progress => Fixed
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #1:
This was fixed in 0.5.12 with the following change:
GPG errors will no longer cause tracebacks, but will produce a
log entry, from gpg, similar to the following:
===== Begin GnuPG log =====
gpg: BAD0BAD0: skipped: public key not found
gpg: [stdin]: encryption failed: public key not found
===== End GnuPG log =====
This will let the user know what really caused the GPG process
to fail, and what really caused errors like 'broken pipe'.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?20234>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
_______________________________________________
Duplicity-tracker mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/duplicity-tracker
