Date: Sat, 28 Jan 2017 10:41:34 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 216543] net/librsync2 Python segfaults Message-ID: <bug-216543-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216543 Bug ID: 216543 Summary: net/librsync2 Python segfaults Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: bdrewery@FreeBSD.org Reporter: freebsdbugs@filis.org Flags: maintainer-feedback?(bdrewery@FreeBSD.org) Assignee: bdrewery@FreeBSD.org There is an issue in librsync 2.0.0 that will be fixed in 2.0.1, which unfortunately isn't released yet: https://github.com/librsync/librsync/issues/50#issuecomment-183803254 I already filed a bug with sysutils/duplicity: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216542 though I'm not quite sure what's the better way to solve this. Maybe backporting the patch for patch.c from here https://github.com/librsync/librsync/commit/09c428e74799937be26be6a165dd6b1= 96e679673?diff=3Dunified#diff-093261456e043e11179c975fc983a1c5 is the easiest since I don't know when 2.0.1 will be released, this issue is more than a year old. --=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-216543-13>