Bug#384826: still continues to fail to work at all

2006-09-06 Thread Rob Browning
Martin Wuertele <[EMAIL PROTECTED]> writes: > Looks like i386 buildd is broken. If I create a fresh i386 chroot, > apt-get -b source duplicity and install it, it runs fine (just what > happened back when 384826 was opened). > > Could you please try to verify, thanks. Certainly. I did an "apt-get

Bug#384826: still continues to fail to work at all

2006-09-06 Thread Martin Wuertele
Hi Rob! * Rob Browning <[EMAIL PROTECTED]> [2006-09-06 12:53]: > reopen 384826 > thanks > > $ dpkg --status duplicity | grep Version > Version: 0.4.2-7 > > $ duplicity > Traceback (most recent call last): > File "/usr/bin/duplicity", line 28, in ? > import getpass, gzip, os, s

Bug#384826: still continues to fail to work at all

2006-09-06 Thread Rob Browning
reopen 384826 thanks $ dpkg --status duplicity | grep Version Version: 0.4.2-7 $ duplicity Traceback (most recent call last): File "/usr/bin/duplicity", line 28, in ? import getpass, gzip, os, sys, time, types, \ ImportError: No module named commandline $ dpkg --listfiles d

Bug#384826: still continues to fail to work at all

2006-08-26 Thread Joey Hess
Package: duplicity Version: 0.4.2-5 Severity: critical [EMAIL PROTECTED]:~>python -V Python 2.4.4c0 [EMAIL PROTECTED]:~>duplicity Traceback (most recent call last): File "/usr/bin/duplicity", line 29, in ? from duplicity import collections, commandline, diffdir, dup_temp, \ ImportError: No m