New question #659529 on Duplicity: https://answers.launchpad.net/duplicity/+question/659529
Hi, I'm not firing a bug because I have the doubt that this could be the programmer's expected behavior, or this could be a RFC instead of a bug. If I pass --gpg-options to duplicity commands that don't do an encryption/decryption, these args never reach gpg command. I found this behavior in a own-maked 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 I want to pass --no-permission-warning to gpg because this script is executed by cron every day (so it is run as root user) to backup some folders of johndoe's home: in this case, without this flag, gpg complains with "gpg: WARNING: unsafe ownership on homedir" message. I'm not a python expert, but as far as I can see this message comes out from command to get mayor version of gpg (class GPGProfile, method get_gpg_major() in file gpg.py). What do you think about this? Thanks in advance Mauro -- You received this question notification because your team duplicity-team is an answer contact for Duplicity. _______________________________________________ Mailing list: https://launchpad.net/~duplicity-team Post to : [email protected] Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
