Processed: Re: Bug#768140: torsocks: FTBFS on kfreebsd-*

2014-11-10 Thread Debian Bug Tracking System
Processing control commands: severity -1 important Bug #768140 [torsocks] torsocks: FTBFS on kfreebsd-* Severity set to 'important' from 'serious' -- 768140: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#768140: torsocks: FTBFS on kfreebsd-*

2014-11-10 Thread intrigeri
Control: severity -1 important (kfreebsd-* aren't release architectures for Jessie.) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#768140: torsocks: FTBFS on kfreebsd-*

2014-11-07 Thread Steven Chamberlain
intrig...@debian.org wrote: The fix for #766306 makes torsocks FTBFS on kfreebsd-*: https://buildd.debian.org/status/package.php?p=torsocks Hi, SO_DOMAIN was only accepted into POSIX earlier this year: http://austingroupbugs.net/view.php?id=840 it seems to be only available yet on Linux and

Bug#768140: torsocks: FTBFS on kfreebsd-*

2014-11-07 Thread Steven Chamberlain
Steven Chamberlain wrote: For FreeBSD I came up with the attached, hackish workaround using SO_TYPE (widely available), and out of the available protocols in PF_LOCAL (= AF_UNIX), assume that only SOCK_{DGRAM,SEQPACKET,STREAM} are candidates for fd passing. Actually it didn't work: | $

Bug#768140: torsocks: FTBFS on kfreebsd-*

2014-11-05 Thread intrigeri
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