Comment 5 for bug 1680682

You are correct, a big chunk of those are invalid, but duplicity should
warn you if they are.

I'll take care of getting your patch into the code, and figuring out what
else is needed.

On Wed, Apr 12, 2017 at 10:07 PM, Dave Allan <email address hidden>
wrote:

> Sorry to be slow responding--I'm out of the office next week and trying
> to wrap some stuff up before I go. You're right that the matrix
> contains a fair number of possible environments, but I'm not sure it's
> necessary to consider them all here. Since the change to 0.7.12 is 2.1
> specific, I'm hoping a patch will be as well. I can work up additional
> patches when I get back if you can expand a bit on what you'd like to
> see.
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1680682
>
> Title:
> --use-agent broken in 0.7.12
>
> Status in Duplicity:
> In Progress
>
> Bug description:
> I've been using gpg2 with --use-agent successfully for a long time,
> but after updating to 0.7.12 my backups started failing with the
> error:
>
> GPGError: GPG Failed, see log below:
> ===== Begin GnuPG log =====
> gpg: Sorry, we are in batchmode - can't get input
> ===== End GnuPG log =====
>
> It seems like the attempt to create truly non-interactive behavior
> (gpg.py at line 140) is causing it to ignore --use-agent.
>
> This seems to be fixed in the most recent code in bzr.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/duplicity/+bug/1680682/+subscriptions
>