severity 384142 serious tag 384142 - unreproducible tag 384142 + confirmed thanks
Pierre HABOUZIT wrote: > tag 384142 + unreproducible > severity 384142 important > thanks I'm sorry, but I can reproduce this on EVERY machine that I run duplicity on, as soon as I upgrade to version 0.4.2-2+sftp+amazons3+compression.2. Machines running 0.4.2-2+sftp+amazons3+compression.1 are ok. This is not unreproducible and is not the result of my dropping files somewhere in the filesystem manually. [EMAIL PROTECTED]:~>dpkg -l duplicity Desired=Unknown/Install/Remove/Purge/Hold |Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:uppercase=bad) ||/ Name Version Description +++-==============-==============-============================================ ii duplicity 0.4.2-2+sftp+a encrypted bandwidth-efficient backup [EMAIL PROTECTED]:~>duplicity Command line error: Too few arguments See the duplicity manual page for instructions [EMAIL PROTECTED]:~>ls -l /usr/lib/python2.3/site-packages/duplicity/__init__.py* -rw-r--r-- 1 root root 0 Feb 2 2006 /usr/lib/python2.3/site-packages/duplicity/__init__.py -rw-r--r-- 1 root root 134 Aug 6 21:09 /usr/lib/python2.3/site-packages/duplicity/__init__.pyc -rw-r--r-- 1 root root 134 Aug 6 21:09 /usr/lib/python2.3/site-packages/duplicity/__init__.pyo [EMAIL PROTECTED]:~>apt-get install duplicity Reading package lists... Done Building dependency tree... Done The following packages will be upgraded: duplicity 1 upgraded, 0 newly installed, 0 to remove and 91 not upgraded. Need to get 0B/99.7kB of archives. After unpacking 49.2kB disk space will be freed. (Reading database ... 29901 files and directories currently installed.) Preparing to replace duplicity 0.4.2-2+sftp+amazons3+compression.1 (using .../duplicity_0.4.2-2+sftp+amazons3+compression.2_i386.deb) ... Unpacking replacement duplicity ... dpkg: warning - unable to delete old directory `/usr/lib/python2.3/site-packages/duplicity': Directory not empty Setting up duplicity (0.4.2-2+sftp+amazons3+compression.2) ... [EMAIL PROTECTED]:~>ls -l /usr/lib/python2.3/site-packages/duplicity/__init__.py* -rw-r--r-- 1 root root 134 Aug 6 21:09 /usr/lib/python2.3/site-packages/duplicity/__init__.pyc -rw-r--r-- 1 root root 134 Aug 6 21:09 /usr/lib/python2.3/site-packages/duplicity/__init__.pyo [EMAIL PROTECTED]:~>duplicity Traceback (most recent call last): File "/usr/bin/duplicity", line 29, in ? from duplicity import collections, commandline, diffdir, dup_temp, \ File "/usr/lib/python2.3/site-packages/duplicity/collections.py", line 22, in ? File "/usr/lib/python2.3/site-packages/duplicity/path.py", line 27, in ? File "/usr/lib/python2.3/site-packages/duplicity/librsync.py", line 26, in ? ImportError: No module named _librsync Conclusion: The files were already put there by the previous version of duplicity, and remain after the upgrade, breaking the new version. > I don't know what's causing that, *but* those files you mention do not > exist in the duplicity package: Bear in mind that python-central and python-support copy files around behind your back, so dpkg -L is not very useful for debugging problems with python packages. > also note that the most recent version in the archive is a binNMU to > work with /usr/bin/python beeing python2.4. I haven't been able to try 0.4.2-2+sftp+amazons3+compression.2+b1, since it's not available for i386: duplicity | 0.4.2-2+sftp+amazons3+compression.2 | unstable | source, alpha, hppa, hurd-i386, i386, ia64 duplicity | 0.4.2-2+sftp+amazons3+compression.2+b1 | unstable | amd64, arm, m68k, mips, mipsel, powerpc, s390, sparc I have no idea if +b1 has this problem or not. But I'd guess that it does. -- see shy jo
signature.asc
Description: Digital signature