I'm also seeing this bug, on two machines. A third machine had the same versions of duplicity, python2.3, and python-central, but did not have the problem; duplicity was installed and working. Then I tried reinstalling it, and reproduced the problem there too:
[EMAIL PROTECTED]:~>sudo apt-get --reinstall install duplicity Password: Reading package lists... Done Building dependency tree... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0B/101kB of archives. After unpacking 0B of additional disk space will be used. Do you want to continue [Y/n]? y (Reading database ... 225992 files and directories currently installed.) Preparing to replace duplicity 0.4.2-10+b1 (using .../duplicity_0.4.2-10+b1_i386.deb) ... INFO: using old version '/usr/bin/python2.3' Unpacking replacement duplicity ... Setting up duplicity (0.4.2-10+b1) ... INFO: using old version '/usr/bin/python2.3' pycentral: pycentral pkginstall: duplicity needs unavailable runtime (2.3) pycentral pkginstall: duplicity needs unavailable runtime (2.3) dpkg: error processing duplicity (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: duplicity E: Sub-process /usr/bin/dpkg returned an error code (1) I also tried downgrading to python-central 0.5.8, but also see it with that version. -- see shy jo
signature.asc
Description: Digital signature