--gpg-options unused with some commands

Hi,

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:

HOME="/home/johndoe"
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

Mauro