On 05 Nov (12:07:03), intrig...@debian.org wrote: > Package: torsocks > Version: 2.0.0-2 > Severity: serious > X-Debbugs-Cc: dgou...@ev0ke.net > Tags: upstream > > The fix for #766306 makes torsocks FTBFS on kfreebsd-*: > > https://buildd.debian.org/status/package.php?p=torsocks > > As said on that other bug (sorry about the confusion, let's please > keep the discussion on this new bug report instead): > > David, may you please have a look?
Hello!
Ok guys, sorry for the delay! That's my mistake, someone reported my
that issue on OS X and I fixed it but it was not pushed upstream!
I just tested on kfreebsd (fischer.debian.org) and it works.
Please see top commit that fixes that:
commit 8406ef884df2fb7dbdfd475ea7e548a40dcdce3f
Author: David Goulet <dgou...@ev0ke.net>
Date: Sat Oct 25 12:33:00 2014 -0400
Fix: use getsockname instead of getsockopt to get socket family
Seems that OS X 10.10 Yosemite does not support the SO_DOMAIN anymore so
use a known compatible call to get the socket family in recv(2).
Fixes #13571
Signed-off-by: David Goulet <dgou...@ev0ke.net>
Again guys, sorry about that. I would encourage you to just pull that
fix since master right now is currently in dev mode for fixing
syscall(). Nothing major for Debian just I would avoid pulling this
commit at least:
"f97b07e 2014-10-24 Stop denying syscall() and add dangerous ones"
Cheers!
David
>
> Time-wise, I'd like to see this bug fixed in Jessie, and the deadline
> to have a fix for an "important" bug is December 5, so it would be
> good to have a fix that doesn't introduce regressions by, say,
> November 20. Does it look doable to you?
>
> Cheers!
signature.asc
Description: Digital signature
