duplicity-team team mailing list archive
-
duplicity-team team
-
Mailing list archive
-
Message #05129
[Question #684523]: ImportError: librsync.so.1: cannot open shared object file
New question #684523 on Duplicity:
https://answers.launchpad.net/duplicity/+question/684523
I've tried following instructions from other links related to this, but it is still not working.
https://serverfault.com/questions/807554/duplicity-0-7-10-fails-after-upgrading-librsync-in-ubuntu-14-04
https://duplicity-talk.nongnu.narkive.com/2tg0Qnxn/problem-with-librsync-so
https://lists.nongnu.org/archive/html/duplicity-talk/2015-05/msg00001.html
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1845599
I also understand that this issue might not be related to duplicity, however if someone could guide me in the right direction it would be really helpful. I've searched StackOverflow, but to no avail.
System: Debian 10
Librsync version 0.9.7-10+b1
Let's say I'm currently in /home/ashish/projects
Steps to reproduce:
1. Install duplicity
sudo apt update
sudo apt install librsync-dev
wget https://code.launchpad.net/duplicity/0.8-series/0.8.04/+download/duplicity-0.8.04.tar.gz
tar xf duplicity-0.8.04.tar.gz
cd duplicity-0.8.04
python3.7 -m venv .venv
source .venv/bin/activate
pip install --upgrade pip
pip install -r requirements.txt
pip install pydrive
./compilec.py
deactivate
2. Run duplicity with pydrive as backend
PYTHONPATH=".:.venv/lib/python3.7/site-packages" ./bin/duplicity . gdocs://username@xxxxxxxxx/backups/duplicity
ERROR:
Traceback (most recent call last):
File "./bin/duplicity", line 55, in <module>
from duplicity.dup_main import main
File "/home/ashish/projects/duplicity-0.8.04/duplicity/dup_main.py", line 56, in <module>
from . import commandline
File "/home/ashish/projects/duplicity-0.8.04/duplicity/commandline.py", line 42, in <module>
from duplicity import backend
File "/home/ashish/projects/duplicity-0.8.04/duplicity/backend.py", line 46, in <module>
from duplicity import dup_temp
File "/home/ashish/projects/duplicity-0.8.04/duplicity/dup_temp.py", line 31, in <module>
from duplicity import path
File "/home/ashish/projects/duplicity-0.8.04/duplicity/path.py", line 47, in <module>
from duplicity import librsync
File "/home/ashish/projects/duplicity-0.8.04/duplicity/librsync.py", line 33, in <module>
from . import _librsync
ImportError: librsync.so.1: cannot open shared object file: No such file or directory
$ ldd duplicity/_librsync.cpython-37m-x86_64-linux-gnu.so
linux-vdso.so.1 (0x00007ffd18366000)
librsync.so.1 => /usr/lib/x86_64-linux-gnu/librsync.so.1 (0x00007f8a0f9c3000)
libpython3.7m.so.1.0 => not found
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f8a0f7a6000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f8a0f407000)
/lib64/ld-linux-x86-64.so.2 (0x00007f8a0fdd5000)
I can clearly see that librsync.so.1 is present in cache using,
$ sudo ldconfig -v | grep librsync
ldconfig: Path `/usr/local/lib' given more than once
ldconfig: Path `/lib/x86_64-linux-gnu' given more than once
ldconfig: Path `/usr/lib/x86_64-linux-gnu' given more than once
ldconfig: /lib/x86_64-linux-gnu/ld-2.24.so is the dynamic linker, ignoring
librsync.so.1 -> librsync.so.1.0.2
$ ls -la /usr/lib/x86_64-linux-gnu/librsync*
lrwxrwxrwx 1 root root 17 Oct 1 08:28 /usr/lib/x86_64-linux-gnu/librsync.so -> librsync.so.1.0.2
lrwxrwxrwx 1 root root 17 Oct 1 08:28 /usr/lib/x86_64-linux-gnu/librsync.so.1 -> librsync.so.1.0.2
-rw-r--r-- 1 root root 56128 Jun 26 2013 /usr/lib/x86_64-linux-gnu/librsync.so.1.0.2
$ ldd /usr/lib/x86_64-linux-gnu/librsync.so
linux-vdso.so.1 (0x00007fff1eb1b000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f124daf2000)
/lib64/ld-linux-x86-64.so.2 (0x00007f124e09f000)
--
You received this question notification because your team duplicity-team
is an answer contact for Duplicity.