FYI, this issue seems to have been resolved with the duplicity-0.8.20-1.1.x86_64 release of duplicity. Thanks!