Re: [Duplicity-talk] GPG error when backing up - invalid option "--pinentry-mode=loopback"

[Kenneth Loafman]

The problem is that gpg 2.0 did not have --pinentry-mode, but gpg 2.1 did.  The fix was to test against major/minor versions rather than just major.

On Thu, Feb 2, 2017 at 11:12 AM, John Covici <address@hidden> wrote:

hmmm, I am using what is supposed to be 0.7.11 and am not seeing this
issue.  My gpg version is 2.1.18.  Just thought I  would let you
know.  I have not tried a restore or verify with this version yet.

On Thu, 02 Feb 2017 11:49:36 -0500,
Kenneth Loafman via Duplicity-talk wrote:
>
> [1  <multipart/alternative (7bit)>]
> [1.1  <text/plain; UTF-8 (7bit)>]
> [1.2  <text/html; UTF-8 (quoted-printable)>]

> The fix has been committed to the trunk in gpg.py. It will be out in 0.7.12. If you need it now, just browse the code for gpg.py, download that, and replace your copy.
>
> ...Ken
>
> On Wed, Feb 1, 2017 at 1:27 PM, Scott Classen via Duplicity-talk <address@hidden> wrote:
>
>  Hello,
>
>  Using installed duplicity version 0.7.11, python 2.7.11, gpg 2.0.14 (Home: ~/.gnupg), awk 'GNU Awk 3.1.7', grep 'grep (GNU grep) 2.20', bash '4.1.2(2)-release (x86_64-redhat-linux-gnu)'.
>
>  [snip]
>
>  GPGError: GPG Failed, see log below:
>  ===== Begin GnuPG log =====
>  gpg: invalid option "--pinentry-mode=loopback"
>
>  the GPG_OPTS variable in my duply conf file is empty.
>
>  What should I do? is there a way to NOT pass the --pinentry-mode=loopback option to gpg?
>
>  Thanks,
>  Scott
>  _______________________________________________
>  Duplicity-talk mailing list
>  address@hidden
>  https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>

> [2  <text/plain; us-ascii (7bit)>]

> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk

--
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         address@hidden