duplicity cannot be expected to parse gpg.conf, no, nor to control gnupg to such an extent. but if duplicity is to call out to gnupg for encryption services, then duplicity can IMO be expected to recover gracefully from catastrophic failures on gnupg's behalf to perform, even when it arguably should not fail.
that gnupg chokes on its own configuration file and dies is gnupg's fault; but that this abnormal termination of gnupg sends duplicity into an endless loop that produces no backup yet never terminates, THAT is duplicity's fault. it would be better for duplicity to detect the fact that gnupg has failed unexpectedly and treat this as an unrecoverable error, passing a failure message on to the user and terminating gracefully. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710309 Title: Backup does not recognize gpg 2 option and fails To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1710309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs