Re: [Duplicity-talk] Cannot restore, runtime throws error

[Tim Riemenschneider]

Am 13.09.2010 12:13, schrieb Yves Goergen:
> I've tried that and the duplicity setup failed:
>   
>> # python setup.py install
>> running install
>> [...]

>> running build_ext
>> building 'duplicity._librsync' extension
>> creating build/temp.linux-x86_64-2.5
>> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
>> -Wstrict-prototypes -fPIC -I/usr/include/python2.5 -c _librsyncmodule.c -o 
>> build/temp.linux-x86_64-2.5/_librsyncmodule.o
>> _librsyncmodule.c:25:20: error: Python.h: No such file or directory
>> _librsyncmodule.c:26:22: error: librsync.h: No such file or directory
>>
>>     
Development files for rsync are missing

apt-get install librsync-dev
should fix that.

cu
Tim