duplicity-talk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] GPG error when backing up - invalid option "--pinen


From: Markus Stoll, junidas GmbH
Subject: Re: [Duplicity-talk] GPG error when backing up - invalid option "--pinentry-mode=loopback"
Date: Thu, 9 Feb 2017 23:07:26 +0100

when fixing gpg.py, I suggest to change the version regex to

    _version_re = re.compile(r'^gpg.*\(GnuPG.*\) 
(?P<maj>[0-9])\.[0-9]+\.[0-9]+$’)

the reason is that on OSX many people have gpg installed as package that 
identifies as

# gpg --version
gpg (GnuPG/MacGPG2) 2.0.30


regards, Markus

> Am 02.02.2017 um 17:49 schrieb Kenneth Loafman via Duplicity-talk 
> <address@hidden>:
> 
> 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
> 
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk

Attachment: smime.p7s
Description: S/MIME cryptographic signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]