Bug 192270 - app-backup/duplicity-0.4.3 requires dev-python/py-gnupg and dev-python/pexpect
Bug#: 192270 Product:  Gentoo Linux Version: 2006.1 Platform: All
OS/Version: Linux Status: RESOLVED Severity: normal Priority: P2
Resolution: FIXED Assigned To: ticho@gentoo.org Reported By: neil@digimed.co.uk
Component: Ebuilds
URL: 
Summary: app-backup/duplicity-0.4.3 requires dev-python/py-gnupg and dev-python/pexpect
Keywords:  
Status Whiteboard: 
Opened: 2007-09-12 08:32 0000
Description:   Opened: 2007-09-12 08:32 0000
After updating duplicity to 0.4.3 I get this when running it

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 29, in <module>
    from duplicity import collections, commandline, diffdir, dup_temp, \
  File
"/var/tmp/portage/app-backup/duplicity-0.4.3/image//usr/lib/python2.5/site-packages/duplicity/collections.py",
line 22, in <module>
  File
"/var/tmp/portage/app-backup/duplicity-0.4.3/image//usr/lib/python2.5/site-packages/duplicity/path.py",
line 649, in <module>
  File
"/var/tmp/portage/app-backup/duplicity-0.4.3/image//usr/lib/python2.5/site-packages/duplicity/gpg.py",
line 22, in <module>
ImportError: No module named GnuPGInterface

The GnuPGInterface module was included in the previous version but has now been
removed and is a separate package, dev-python/py-gnupg. pexpect is also
required.

Explanation:
http://article.gmane.org/gmane.comp.sysutils.backup.duplicity.general/1003

After emerging dev-python/py-gnupg-0.3.2 and dev-python/pexpect-2.1, duplicity
is working again. Can you add these as RDEPENDS?

------- Comment #1 From Andrej Kacian (RETIRED) 2007-09-12 12:05:04 0000 -------
It works without pexpect here...

------- Comment #2 From Andrej Kacian (RETIRED) 2007-09-12 13:18:48 0000 -------
...but after some digging, I found out that the duplicity code uses pexpect at
some places. Both py-gnupg and pexpect were added to RDEPEND. Thanks!

------- Comment #3 From Neil Bothwick 2007-09-12 14:03:36 0000 -------
It barfed on the missing pexpect as soon as I ran it. Does it only affect
--encrypt-key, the only other arguments I used were --include and --exclude?

Anyway, thanks for the quick fix.