There is a new version of duplicity (v0.6.06) upstream. The new version includes a fix which is critical for anyone using duplicity as part of a cron job or other automated script (which I would guess is almost everyone). v0.6.05 ALWAYS prompts for a GPG passphrase, even when it isn't needed, as compared to older versions that only prompt when it is actually needed. So anyone using duplicity in a cron job will suddenly find all of their duplicity backups failing since it can't get the GPG passphrase (which it doesn't actually need). A temporary workaround which works in most cases is to set the PASSPHRASE environment variable (it doesn't need to be set to the actual GPG passphrase since, again, it doesn't actually use the passphrase anywhere)
I've commited duplicity-0.6.06-1 to CVS and will push it as update for all active Fedora and EPEL branches. Thanks for your report.
duplicity-0.6.06-1.el4 has been submitted as an update for Fedora EPEL 4. http://admin.fedoraproject.org/updates/duplicity-0.6.06-1.el4
duplicity-0.6.06-1.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/duplicity-0.6.06-1.fc11
duplicity-0.6.06-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/duplicity-0.6.06-1.fc12
duplicity-0.6.06-1.el5 has been submitted as an update for Fedora EPEL 5. http://admin.fedoraproject.org/updates/duplicity-0.6.06-1.el5
duplicity-0.6.06-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
duplicity-0.6.06-1.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
duplicity-0.6.06-1.el4 has been pushed to the Fedora EPEL 4 stable repository. If problems still persist, please make note of it in this bug report.
duplicity-0.6.06-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.