It doesn't break gpg1, and I'm successfully using gpg2 with separate encryption and signing keys. I have tested also without using gpg-agent, and that works fine.
On Sep 6, 2011, at 3:45 PM, edso <[email protected]> wrote: > On 06.09.2011 20:59, Ross Williams wrote: >> Ross Williams has proposed merging >> lp:~ross-ross-williams/duplicity/gpg-agent-fix into lp:duplicity. >> >> Requested reviews: >> duplicity-team (duplicity-team) >> Related bugs: >> Bug #842990 in Duplicity: "use-agent doesn't work with gpg2" >> https://bugs.launchpad.net/duplicity/+bug/842990 >> >> For more details, see: >> https://code.launchpad.net/~ross-ross-williams/duplicity/gpg-agent-fix/+merge/74278 >> >> Have gpg.py check whether use_agent is enabled before asking GnuPGInterface >> to create a passphrase file descriptor. This works around a GnuPG >> 2.x-related issue in which --passphrase-fd takes priority over --use-agent >> as the source of the passphrase. The opposite was true in GnuPG 1.x, so this >> bug only occurs when using gpg2. > > > nice.. does it work for gpg1 and 2 now? ..ede/duply.net > > -- > https://code.launchpad.net/~ross-ross-williams/duplicity/gpg-agent-fix/+merge/74278 > You are the owner of lp:~ross-ross-williams/duplicity/gpg-agent-fix. -- https://code.launchpad.net/~ross-ross-williams/duplicity/gpg-agent-fix/+merge/74278 Your team duplicity-team is requested to review the proposed merge of lp:~ross-ross-williams/duplicity/gpg-agent-fix into lp:duplicity. _______________________________________________ Mailing list: https://launchpad.net/~duplicity-team Post to : [email protected] Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
