Since the upstream release duplicity-0.6.15 has broken GPG support beyond usefulness, please mask this ebuild and version bump to the fixed 0.6.16 release. Thanks! Reproducible: Always Here's my upstream bugreport: > Hi Kenneth > > I've got your email from the Duplicity changelog as you've been working on > this topic. After a recent update of both duplicity (0.6.15) and gnupg > (2.0.18) on my box, the backups don't work anymore as the GPG key is not > read from the PASSPHRASE environment variable anymore. The documentation > doesn't state any changes, do you have an idea what could be the problem? > > Here's the exact error message from the cronjob: > /usr/lib64/python2.7/getpass.py:83: GetPassWarning: Can not control echo > on the terminal. > passwd = fallback_getpass(prompt, stream) > > When I start the script manually, the PASSPHRASE env variable is set to > the correct passphrase, still duplicity prompts for the passphrase and > sign passphrase. And the reply: > Thanks for the info. The bug is fixed in the repository and will be in the > next release. > > ...Ken
Last night's run of 0.6.16 powered backup showed a new, blocking bug with this version which renders s3 support unusable. I thus zap this version bump request.
Last version known to work is 0.6.14 (not currently in the portage tree).