--gpg-binary option not working
Bug #1655268 reported by
Kohei YOSHIDA
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
Medium
|
Unassigned |
Bug Description
An instance of gpg.GPGProfile is created at commandline.py:1092 before parse_cmdline_
Duplicity version:
0.7.11
Python version:
2.7.10
OS Distro and version:
Mac OS X El Capitan 10.11.6
Type of target filesystem:
Journaled HFS+
Log output from -v9 option:
duplicity -v9 --gpg-binary /usr/local/bin/gpg2
GPGError: failed to determine gpg version of None from gpg (GnuPG/MacGPG2) 2.0.30
Changed in duplicity: | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Kenneth Loafman (kenneth-loafman) |
Changed in duplicity: | |
assignee: | Kenneth Loafman (kenneth-loafman) → nobody |
milestone: | none → 0.7.12 |
status: | In Progress → Fix Committed |
Changed in duplicity: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I think this is not a duplicate of bug #1654220.
The problem I reported here is `--gpg-version command line parameter is always ignored by duplicity`. Due to this problem, I could not choose another version of GPG (non-MacGPG), so I affect bug #1654220 and cannot avoid it.