Follow-up Comment #10, bug #21792 (project duplicity): No, actually its called during the build of the temp file that the backends then send to remote. Sorry, but that patch would have nothing to do with it. Not enough coffee this morning. ;-)
Duplicity uses process.wait() to wait for the child process to complete. process.wait() is a wrapper to os.waitpid(process.pid, 0), so the task should be complete and go away. I'm not sure why its not. This bug has been reported on the GnuPGInterface web site, but there is no resolution as yet. It was reported anonymously, so I'm sure there is little communication going on with the reporter. I left a comment so I would be notified if there is progress. https://sourceforge.net/tracker/index.php?func=detail&aid=1850121&group_id=29555&atid=396632 _______________________________________________________ Reply to this item at: <http://savannah.nongnu.org/bugs/?21792> _______________________________________________ Message sent via/by Savannah http://savannah.nongnu.org/ _______________________________________________ Duplicity-tracker mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/duplicity-tracker
