This is not something duplicity controls.  If gpg is saying that it does
not recognize the trust model supplied in gpg.conf, then the bug could
be that the version of gpg on the system is too old for this trust
model.  It is not in duplicity since duplicity has no reason to read
gpg.conf.  Perhaps running a test encryption after changing gpg.conf
would have shown the problem?
** Changed in: duplicity
       Status: New => Invalid

-- 
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

Reply via email to