--gpg-options unused with some commands
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Hi,
bug created from question #659529.
If I pass --gpg-options to duplicity commands that don't do an encryption/
I found this behavior in a own-maked cron.daily duplicity script, where before do an encryption I issue a cleanup command like this:
HOME="/
duplicity cleanup --gpg-options=
Script sets HOME to johndoe's home to use johndoe's gpg key, but given that cron runs script as root user, gpg complains with "gpg: WARNING: unsafe ownership on homedir" message, therefore need to pass --no-permission
I'm not a python expert, but as far as I can see this message comes out because call to get major version of gpg (class GPGProfile, method get_gpg_major() in file gpg.py) doesn't use --gpg-options.
Is it possible to pass --gpg-options to the get version call?
Thanks in advance
Mauro
Changed in duplicity: | |
assignee: | nobody → Kenneth Loafman (kenneth-loafman) |
importance: | Undecided → Medium |
milestone: | none → 0.7.15 |
status: | New → In Progress |
Changed in duplicity: | |
status: | In Progress → Won't Fix |
status: | Won't Fix → Fix Released |
assignee: | Kenneth Loafman (kenneth-loafman) → nobody |
Changed in duplicity: | |
status: | Fix Released → Fix Committed |
Changed in duplicity: | |
status: | Fix Committed → Fix Released |
Thank you very much!