Date: Wed, 12 Jul 2017 13:12:17 +0200 From: Stefan Esser <se@freebsd.org> To: freebsd-ports@freebsd.org Cc: Rainer Hurling <rhurlin@gwdg.de>, duglas <duglas@bigpond.net.au> Subject: Re: Update failure E000022 after upgrade to subversion 1.9.6 Message-ID: <580789c0-c5f3-91a4-fed0-090e50f44b9e@freebsd.org> In-Reply-To: <e1bf2bb1-f30a-82ca-18cd-e1e6e6ecaab9@gwdg.de> References: <6d403c58-8eb6-806f-14bd-40717f1e3ad8@bigpond.net.au> <a37d735c-6bef-e605-4c96-d730f56150d4@FreeBSD.org> <e1bf2bb1-f30a-82ca-18cd-e1e6e6ecaab9@gwdg.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 12.07.17 um 07:42 schrieb Rainer Hurling: > Hi duglas@ > > I had the same problem. I completely solved it by rebuilding the > dependency chain of devel/subversion: > > portmaster serf-1.3.9_1 expat-2.2.1 gettext-runtime-0.19.8.1_1 > apr-1.5.2.1.5.4_2 sqlite3-3.19.3_1 subversion-1.9.6 > > Probably, only one of them is the culprit, but I haven't testet ;) I have, and it appears to have been devel/apr1 ... After rebuilding first apr and then subversion, the problem is resolved on my system. The cause seems to have been the ino64 change, which is visible from the userland. Library versioning should take care of that, but that does not work, if subversion wants the new version and apr needs the old one ... Other ports could be affected as well, if they link against a library that needs an old version of a C library function, while the binary was built for the new call signature. As long as ports are built with or without the ino64 change, they should continue to work (and thus, -STABLE packages are not affected). Regards, STefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?580789c0-c5f3-91a4-fed0-090e50f44b9e>