If you look at the postinst script in the deb, the problem is clear: It never runs python-support, so the modules come up missing:
Preparing to replace duplicity 0.4.2-2+sftp+amazons3+compression.2 (using .../duplicity_0.4.2-5_i386.deb) ... Unpacking replacement duplicity ... Setting up duplicity (0.4.2-5) ... [EMAIL PROTECTED]:~>cat /var/lib/dpkg/info/duplicity.p* #!/bin/sh -e # Source debconf library. . /usr/share/debconf/confmodule #!/bin/sh -e # fix my previous errors rm -rf /usr/lib/python2.2/site-packages/duplicity/ rm -rf /usr/lib/python2.3/site-packages/duplicity/ [EMAIL PROTECTED]:~> (BTW, that debconf stuff has no need to be there.) I can't explain why it works on the maintainer's system, besides hypothesising that he may have the installed library files left behind somehow. I can certianly reproduce the problem here, on all my systems (which have all been w/o backups for a week+ now due to the previous problem and this one). Strangest of all, simply rebuilding the package fixes the problem; dh_pysupport does its thing and adds code to the postinst and prerm that isn't there in the deb in the archive. Possibly the version in the archive is just a bad build. -- see shy jo
signature.asc
Description: Digital signature
