Date: Sat, 28 Jan 2017 10:29:08 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 216542] sysutils/duplicity Python segfaults, related to librsync 2.0.0? Message-ID: <bug-216542-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216542 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@FreeBSD.org Reporter: freebsdbugs@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 segfa= ult 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? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-216542-13>