It looks like problem in www/serf cause devel/subversion to core dump in some situations. More (and fix) could be found in this forum thread: https://forums.freebsd.org/viewtopic.php?f=43&t=46620&p=260580#p260580
Created attachment 143499 [details] serf-1.3.5/outgoing.c patch
Hm, the subversion user mailing lists is full of error reports but there is no concrete patch or a new serf available. In the list there is a hint to serf r2361 however serf has changed so many code the file cannot be used as drop in replacement. Since I'm using subversion17 anywhere in production I have no real test case. Please test the attached patch, build is OK. PS: Since subversion18 is the main consumer of serf would you as subversion18 maintainer mind to take over this port?
A commit references this bug: Author: ohauer Date: Sun Jun 8 16:26:52 UTC 2014 New revision: 357053 URL: http://svnweb.freebsd.org/changeset/ports/357053 Log: - possible fix for all the subversion18 failures reported on the subversion-user list and on forums.freebsd.org - bump PORTREVISION PR: ports/190757 Submitted by: lev Obtained from: https://forums.freebsd.org/viewtopic.php?p=260727#p260727 Changes: head/www/serf/Makefile head/www/serf/files/patch-outgoing.c
The patch was committed, A quick grep shows there are only three main serf consumers. - editors/openoffice-4 - editors/openoffice-devel - devel/subversion (~150 ports depending on devel/subversion) So to keep response times for devel/subversion short I would prefer to assign serf to the subversion maintainer lev@ (you) or the ports@ pool.
Looks like latest www/serf works Ok.