Duplicity 0.7.11 broken with GnuPG 2.0

Bug #1658283 reported by Toni Viemerö
54
This bug affects 9 people
Affects Status Importance Assigned to Milestone
Duplicity
Fix Released
Medium
Unassigned

Bug Description

Duplicity 0.7.11 introduced a new "--pinentry-mode=loopback" gpg param. This change broke Duplicity on Linuxes running GnuPG <2.1.

"--pinentry-mode" isn't available in GnuPG 2.0. Only in 2.1.

I'm unfamiliar with Launchpad and unable to provide a pull request, but the problem lies in duplicity/gpg.py file, line 142.

GnuPG 2.0:
⇒ gpg --version
gpg (GnuPG) 2.0.22
⇒ gpg --pinentry-mode=loopback
gpg: invalid option "--pinentry-mode=loopback"

GnuPG 2.1:
⇒ gpg --version
gpg (GnuPG) 2.1.15
⇒ gpg --pinentry-mode=loopback
gpg: Go ahead and type your message ...

Changed in duplicity:
importance: Undecided → Medium
milestone: none → 0.7.12
status: New → Fix Committed
Revision history for this message
Troels Arvin (troels-w) wrote :

Link to related bug report for EPEL 7:
https://bugzilla.redhat.com/show_bug.cgi?id=1415177

Revision history for this message
Stephen Haffner (yupyupp) wrote :

On CentOS 7.3.1611 "--pinentry-mode mode" does not work but is listed in the manpage for GnuPG 2.0.22:

https://bugs.centos.org/view.php?id=12706

Changed in duplicity:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.