Update failure E000022 after upgrade to subversion 1.9.6
duglas at bigpond.net.au
Wed Jul 12 13:18:47 UTC 2017
Thank you all kindly for you input.
I'd not previously set any locale at all. Setting my locale in
~/.login_conf as below enables me to run svn updates again.
I chose my lang by checking the output from,
locale -a | grep '\.UTF-8$'
Strangely the "svn status" command then seg faulted on me which it
didn't previously. This seemed to begin after the 1.9.6 update and
before (and after) setting my locale as above.
I then rebuilt devel/apr1 and devel/subversion as mentioned by Stefan.
Things seem healthier again with both "svn update" and "svn status".
However I now get the following when running "svn update /usr/ports"
svn: E175002: Unexpected HTTP status 400 'Bad Request' on '/ports/!svn/me'
Perhaps this is unrelated to the above issues I was experiencing.
I'd meant to respond sooner but my incompetence and unfamiliarity with
the mailman system prevented me doing so promptly ;)
On 12/07/2017 9:12 PM, Stefan Esser wrote:
> 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-188.8.131.52.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
More information about the freebsd-ports