Public bug reported:

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)

** Affects: duplicity (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug eoan regression-update

** Summary changed:

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1845599

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

Status in duplicity package in Ubuntu:
  New

Bug description:
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1845599/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to