eoan regression: ImportError: librsync.so.1: cannot open shared object file: No such file or directory

[Eugene Crosser]

After yesterday's upgrade, librsync2 is 2.0.2-1, it's shared object name is

    /usr/lib/x86_64-linux-gnu/librsync.so.2

but duplicity's _librsync.so wants librsync.so.1:

    etc/cron.daily/dbackup:
    Traceback (most recent call last):
      File "/usr/local/bin/duplicity", line 47, in <module>
        from duplicity import collections
      File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", line 32, in <module>
        from duplicity import path
      File "/usr/local/lib/python2.7/dist-packages/duplicity/path.py", line 44, in <module>
        from duplicity import librsync
      File "/usr/local/lib/python2.7/dist-packages/duplicity/librsync.py", line 30, in <module>
        from . import _librsync
    ImportError: librsync.so.1: cannot open shared object file: No such file or directory

Does the package need to be rebuilt, perhaps?

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: duplicity 0.8.04-2
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Fri Sep 27 09:00:31 2019
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)

[Robie Basak (racb)]

Thank you for your report.

This looks like a local configuration problem, rather than a bug in Ubuntu.

Specifically it looks like you have a locally installed version of duplicity in /usr/local/, rather than using one from an Ubuntu package. Any rebuilding necessary is therefore up to you, and not a bug in Ubuntu.

On Eoan with duplicity 0.8.04-2ubuntu1:

$ ldd /usr/lib/python3/dist-packages/duplicity/_librsync.cpython-37m-x86_64-linux-gnu.so
        linux-vdso.so.1 (0x00007ffff4cdf000)
        librsync.so.2 => /lib/x86_64-linux-gnu/librsync.so.2 (0x00007f84e3605000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f84e35e2000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f84e33f1000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f84e3624000)

You can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Since we use this bug tracker to track bugs in Ubuntu, rather than configuration problems, I'm marking this bug as Invalid. This helps us to focus on fixing bugs in Ubuntu.

If you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide full steps to reproduce, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

I'll also change regression-update to regression-release according to https://wiki.ubuntu.com/Bugs/Tags, since this isn't a claimed regression in a stable release.

[Eugene Crosser (crosser)]

Indeed. When I thought that I switched to distro-provided package a few years back, I forgot to update the path in my cron script. Sorry for the confusion.