Re: Update failure E000022 after upgrade to subversion 1.9.6
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. me:\ :charset=UTF-8:\ :lang=en_AU.UTF-8:\ :setenv=LC_COLLATE=C: 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-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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Update failure E000022 after upgrade to subversion 1.9.6
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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Update failure E000022 after upgrade to subversion 1.9.6
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 ;) Best wishes, Rainer Hurling Am 11.07.2017 um 18:33 schrieb Torsten Zuehlsdorff: On 11.07.2017 17:17, duglas wrote: Hi, After upgrading to subversion 1.9.6 My latest svn update attempts result in the following. svn update /usr/ports Updating 'ports': svn: E22: Error converting entry in directory '/usr/ports' to UTF-8 svn: E22: Can't convert string from native encoding to 'UTF-8': svn: E22: ?\A89' Coincidentally it also occurs when attempting to update /usr/src and /usr/docs as well. Attempts to portdowngrade to the 1.9.5 version fail similarly. Are you sure that this is an update problem? I remember this error back some time. It occurs only when having non-native file names like "Überraschung.txt" in the repo while using a shell without having correct encoding set. (Beside: it works for me without the problems you describe :D) Greetings, Torsten ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Update failure E000022 after upgrade to subversion 1.9.6
On 11.07.2017 17:17, duglas wrote: Hi, After upgrading to subversion 1.9.6 My latest svn update attempts result in the following. svn update /usr/ports Updating 'ports': svn: E22: Error converting entry in directory '/usr/ports' to UTF-8 svn: E22: Can't convert string from native encoding to 'UTF-8': svn: E22: ?\A89' Coincidentally it also occurs when attempting to update /usr/src and /usr/docs as well. Attempts to portdowngrade to the 1.9.5 version fail similarly. Are you sure that this is an update problem? I remember this error back some time. It occurs only when having non-native file names like "Überraschung.txt" in the repo while using a shell without having correct encoding set. (Beside: it works for me without the problems you describe :D) Greetings, Torsten -- Support me at: https://www.patreon.com/TorstenZuehlsdorff ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
