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> AAAAAAAAAAAAAAAAAARRRRRRRRRRRRRRRRRRGGGGGGGGGGGGGLLLLLLLLLLL!!!!!
<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]
