Bug#384142: fails to work with python 2.3.5
Hi Joey! * Joey Hess [EMAIL PROTECTED] [2006-08-22 07:55]: [EMAIL PROTECTED]:~python -V Python 2.3.5 [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 If I rebuild the package with current python (2.4) from sid it works, i I rebuild it it with pythong 2.3 from sid or from testing it works as well. However building with the default python in sid results in a python 2.4 dependency. I therefore prefere to build against sid default python making duplicity work again but not really fixing your bug. Do you really need a version of duplicity working with python 2.3? yours Martin -- [EMAIL PROTECTED] Debian GNU/Linux - The Universal Operating System Tolimar AARRGLLL! Tolimar Da gibt es ein Welche Linux Distribution ist fuer dich die richtige-Quiz, und die schalgen mir Ubuntu vor! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#384142: fails to work with python 2.3.5
tag 384142 + unreproducible severity 384142 important thanks On Tue, Aug 22, 2006 at 01:45:05AM -0400, Joey Hess wrote: Package: duplicity Version: 0.4.2-2+sftp+amazons3+compression.2 Severity: serious [EMAIL PROTECTED]:~python -V Python 2.3.5 [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 I don't know what's causing that, *but* those files you mention do not exist in the duplicity package: dpkg --contents duplicity_0.4.2-2+sftp+amazons3+compression.2_i386.deb drwxr-xr-x root/root 0 2006-08-12 23:38 ./ drwxr-xr-x root/root 0 2006-08-12 23:38 ./usr/ drwxr-xr-x root/root 0 2006-08-12 23:38 ./usr/bin/ -rwxr-xr-x root/root 7287 2006-08-12 23:38 ./usr/bin/rdiffdir -rwxr-xr-x root/root 14188 2006-08-12 23:38 ./usr/bin/duplicity drwxr-xr-x root/root 0 2006-08-12 23:38 ./usr/lib/ drwxr-xr-x root/root 0 2006-08-12 23:38 ./usr/lib/python-support/ drwxr-xr-x root/root 0 2006-08-12 23:38 ./usr/lib/python-support/duplicity/ drwxr-xr-x root/root 0 2006-08-12 23:38 ./usr/lib/python-support/duplicity/python2.3/ drwxr-xr-x root/root 0 2006-08-12 23:38 ./usr/lib/python-support/duplicity/python2.3/duplicity/ -rw-r--r-- root/root 8896 2006-08-12 23:38 ./usr/lib/python-support/duplicity/python2.3/duplicity/_librsync.so drwxr-xr-x root/root 0 2006-08-12 23:38 ./usr/share/ drwxr-xr-x root/root 0 2006-08-12 23:38 ./usr/share/man/ drwxr-xr-x root/root 0 2006-08-12 23:38 ./usr/share/man/man1/ -rw-r--r-- root/root 7081 2006-08-12 23:38 ./usr/share/man/man1/duplicity.1.gz -rw-r--r-- root/root 804 2006-02-03 04:44 ./usr/share/man/man1/rdiffdir.1.gz drwxr-xr-x root/root 0 2006-08-12 23:38 ./usr/share/doc/ drwxr-xr-x root/root 0 2006-08-12 23:38 ./usr/share/doc/duplicity/ -rw-r--r-- root/root 970 2006-02-03 04:44 ./usr/share/doc/duplicity/README -rw-r--r-- root/root 1833 2006-08-12 23:38 ./usr/share/doc/duplicity/copyright -rw-r--r-- root/root 1293 2006-08-12 23:38 ./usr/share/doc/duplicity/changelog.Debian.gz -rw-r--r-- root/root 3068 2006-02-03 04:44 ./usr/share/doc/duplicity/changelog.gz drwxr-xr-x root/root 0 2006-08-12 23:38 ./usr/share/python-support/ drwxr-xr-x root/root 0 2006-08-12 23:38 ./usr/share/python-support/duplicity/ drwxr-xr-x root/root 0 2006-08-12 23:38 ./usr/share/python-support/duplicity/duplicity/ -rw-r--r-- root/root 20113 2006-02-03 04:44 ./usr/share/python-support/duplicity/duplicity/path.py -rw-r--r-- root/root 16616 2006-02-03 04:44 ./usr/share/python-support/duplicity/duplicity/patchdir.py -rw-r--r-- root/root 6579 2006-02-03 04:44 ./usr/share/python-support/duplicity/duplicity/librsync.py -rw-r--r-- root/root 8530 2006-02-03 04:44 ./usr/share/python-support/duplicity/duplicity/file_naming.py -rw-r--r-- root/root 1405 2006-02-03 04:44 ./usr/share/python-support/duplicity/duplicity/static.py -rw-r--r-- root/root 11252 2006-02-03 04:44 ./usr/share/python-support/duplicity/duplicity/lazy.py -rw-r--r-- root/root 10071 2006-02-03 04:44 ./usr/share/python-support/duplicity/duplicity/manifest.py -rw-r--r-- root/root 7780 2006-02-03 04:44 ./usr/share/python-support/duplicity/duplicity/dup_time.py -rwxr-xr-x root/root 58918 2006-02-03 04:44 ./usr/share/python-support/duplicity/duplicity/tarfile.py -rw-r--r-- root/root 9916 2006-08-12 23:38 ./usr/share/python-support/duplicity/duplicity/gpg.py -rw-r--r-- root/root 9837 2006-02-03 04:44 ./usr/share/python-support/duplicity/duplicity/statistics.py -rw-r--r-- root/root 1429 2006-02-03 04:44 ./usr/share/python-support/duplicity/duplicity/log.py -rw-r--r-- root/root 2837 2006-02-03 04:44 ./usr/share/python-support/duplicity/duplicity/globals.py -rw-r--r-- root/root 19269 2006-02-03 04:44 ./usr/share/python-support/duplicity/duplicity/selection.py -rw-r--r-- root/root 10453 2006-08-12 23:38 ./usr/share/python-support/duplicity/duplicity/commandline.py -rw-r--r-- root/root 23723 2006-02-03 04:44 ./usr/share/python-support/duplicity/duplicity/collections.py -rw-r--r-- root/root 15353 2006-08-12 23:38 ./usr/share/python-support/duplicity/duplicity/backends.py -rw-r--r-- root/root 0 2006-02-03 04:44 ./usr/share/python-support/duplicity/duplicity/__init__.py -rw-r--r-- root/root 1954 2006-02-03 04:44 ./usr/share/python-support/duplicity/duplicity/robust.py -rw-r--r-- root/root 4957 2006-02-03 04:44 ./usr/share/python-support/duplicity/duplicity/misc.py -rw-r--r--
Bug#384142: fails to work with python 2.3.5
Joey Hess wrote: 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 Ah, right, .pyc and .pyo, but no .py files remain. The .pyc etc files are left behind after the upgrade, since the old version of duplicity is broken and has a postinst that runs compileall, but no prerm to remove the old compiled files. If you had used debhelper, this wouldn't have happened, but since you didn't, you're left needing to clean this mess up in the postinst when the package is upgraded to a new version. -- see shy jo signature.asc Description: Digital signature
Bug#384142: fails to work with python 2.3.5
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 VersionDescription +++-==-==- 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
Bug#384142: fails to work with python 2.3.5
Le mar 22 août 2006 19:18, Joey Hess a écrit : Joey Hess wrote: 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 Ah, right, .pyc and .pyo, but no .py files remain. The .pyc etc files are left behind after the upgrade, since the old version of duplicity is broken and has a postinst that runs compileall, but no prerm to remove the old compiled files. If you had used debhelper, this wouldn't have happened, but since you didn't, you're left needing to clean this mess up in the postinst when the package is upgraded to a new version. s/me/maxx/ I only did the last NMU, and failed to see that the previous package was completely braindead wrt that pyo/pyc cleaning. I'll let the maintainer clean that, and you're right, the severity has to be raised. I suppose the correct fix is to: rm -rf /usr/lib/python2.3/site-packages/duplicity/ somewhere in the preinst *eek*. I only answered because I do monitor the packages I NMUed for the python policy update, but here it's not a bug I did created (I just revealed it) so the maintainer really has to fix it. Cheers, -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpom7x2nUPgV.pgp Description: PGP signature
Bug#384142: fails to work with python 2.3.5
Martin Wuertele wrote: If I rebuild the package with current python (2.4) from sid it works, i I rebuild it it with pythong 2.3 from sid or from testing it works as well. However building with the default python in sid results in a python 2.4 dependency. I therefore prefere to build against sid default python making duplicity work again but not really fixing your bug. See my other messages for an analysis of what needs to be done to fix the bug. rebuild won't cut it. Do you really need a version of duplicity working with python 2.3? I don't care what version of python it works with. However, I *do* need a /usr/bin/duplicity that runs, rather than backtracing. -- see shy jo signature.asc Description: Digital signature
Bug#384142: fails to work with python 2.3.5
Package: duplicity Version: 0.4.2-2+sftp+amazons3+compression.2 Severity: serious [EMAIL PROTECTED]:~python -V Python 2.3.5 [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 -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages duplicity depends on: ii gnupg1.4.5-1 GNU privacy guard - a free PGP rep ii libc62.3.6.ds1-2 GNU C Library: Shared libraries ii librsync10.9.7-1 Library which implements the rsync ii python 2.3.5-11An interactive high-level object-o ii python-gnupginterface0.3.2-9 Python interface to GnuPG (GPG) ii python-support 0.4.1 automated rebuilding support for p duplicity recommends no packages. -- no debconf information -- see shy jo signature.asc Description: Digital signature
