Summary: | net/torsocks: Unsupported syscall errors in version 2.3.0 | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Stefan Ehmann <shoesoft> | ||||||
Component: | Individual Port(s) | Assignee: | Yuri Victorovich <yuri> | ||||||
Status: | Closed FIXED | ||||||||
Severity: | Affects Only Me | CC: | manas, ndowens04 | ||||||
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(yuri) |
||||||
Version: | Latest | ||||||||
Hardware: | Any | ||||||||
OS: | Any | ||||||||
URL: | https://trac.torproject.org/projects/tor/ticket/28688 | ||||||||
Attachments: |
|
Description
Stefan Ehmann
2018-12-02 22:02:10 UTC
Created attachment 199769 [details]
Attempt
Try this patch, if it works; we can update the port and fix this
(In reply to Nathan from comment #1) Hi Nathan, This patch doesn't apply, because this file is already patched for accept4 vs. accept by the port patch. It doesn't even contain the notion of 'accept4' any more. Yuri I see this issue too, I have locked the torsocks package on my systems for the time being. Created attachment 202618 [details]
updated syscall patch
files/patch-src_lib_torsocks.c was deleted during the upgrade to 2.3.0 but patching still seems to be necessary.
Attached is a version that applies against torsocks 2.3.0. At least my use case is working again.
Committed. Thank you for the patch! A commit references this bug: Author: yuri Date: Wed Mar 6 05:00:28 UTC 2019 New revision: 494775 URL: https://svnweb.freebsd.org/changeset/ports/494775 Log: net/torsocks: Fix unsupported syscall errors in version 2.3.0 PR: 233736 Submitted by: Stefan Ehmann <shoesoft@gmx.net> Changes: head/net/torsocks/Makefile head/net/torsocks/files/patch-src_lib_syscall.c |