Re: [Duplicity-talk] request: print gpg errors on verbosity 4

[Kenneth Loafman]

address@hidden wrote:
> hello ken and all,
> 
> I am just working on dealing with gpg errors like the untrusted key and
> I have to admit that I dislike the current behaviour of showing the
> python error stack at verbosity 4 but not the reason for it ....
> verbosity 5 on the other hand is no option as it prints out the ncftp
> traffic that is not concerning to the everyday user
> 
> please move the gpg error printout to verbosity 4 also .. so that one
> can see why there is a broken pipe
> 
>    return self.gpg_input.write(buf)
> IOError: [Errno 32] Broken pipe

The last version should have gpg error output printing any time an error
occurs, regardless of verbosity.  If its not, please show me a longer
piece of the log so I can see why not.

...Ken

signature.asc
Description: OpenPGP digital signature