--gpg-options unused with some commands

Bug #1724144 reported by Mauro S on 2017-10-17
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description


bug created from question #659529.

If I pass --gpg-options to duplicity commands that don't do an encryption/decryption, these args aren't forwarded to gpg command.

I found this behavior in a own-maked cron.daily duplicity script, where before do an encryption I issue a cleanup command like this:

duplicity cleanup --gpg-options="--no-permission-warning" --force $TARGET_DIR

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-warning with --gpg-options.

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


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
Mauro S (mauro-salvini) wrote :

Thank you very much!

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

Other bug subscribers

Related questions