[Bug 216542] sysutils/duplicity Python segfaults, related to librsync 2.0.0?

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216542

            Bug ID: 216542
           Summary: sysutils/duplicity Python segfaults, related to
                    librsync 2.0.0?
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: freebsdbugs at filis.org

After we upgraded a couple of boxes to duplicity with the new librsync2
dependency, Python starts segfaulting, when there are backup sets in place. So
we started new chains yesterday and today's backup scripts let Python segfault
again. I searched around a bit and it seems, someone already filed an issue
related to librsync2 here

https://answers.launchpad.net/duplicity/+question/284756

that links to this librsync2 PR

https://github.com/librsync/librsync/issues/50#issuecomment-183803254

and this relates to what we got in the core dump:

...
#0  0x0000000805c7f7df in rs_search_for_block () from
/usr/local/lib/librsync.so.2
[New Thread 8086e5c00 (LWP 100222/<unknown>)]
[New Thread 8084f3000 (LWP 100418/<unknown>)]
[New Thread 802006400 (LWP 101415/<unknown>)]

So could we maybe go back to librsync1 until this is fixed in librsync 2.0.1 or
import the patch?

-- 
You are receiving this mail because:
You are the assignee for the bug.