On Fri, Oct 12, 2012 at 12:45:41AM +0200, Janek wrote: > svn lock fails if filename contains special character (utf8) > > env > LC_ALL=pl_PL.UTF-8 > > naox@sv1 [/home/naox]# svn co https://svn.naox.vipserv.org/ test > Pobrano wersję 0. > naox@sv1 [/home/naox]# cd test > naox@sv1 [/home/naox/test]# touch file1 > naox@sv1 [/home/naox/test]# touch file2ząb > naox@sv1 [/home/naox/test]# svn add file1 > A file1 > naox@sv1 [/home/naox/test]# svn add file2ząb > A file2ząb > naox@sv1 [/home/naox/test]# svn commit > Dodawanie file1 > Dodawanie file2ząb > Przesyłanie treści pliku.. > Committed revision 1. > naox@sv1 [/home/naox/test]# svn lock file1 > 'file1' zablokowane przez użytkownika 'test'. > naox@sv1 [/home/naox/test]# svn lock file2ząb > svn: E165001: Failed to start '/home/naox/svn/llo/hooks/pre-lock' hook > > Lock would work with this diacritic character in filename if > /home/naox/svn/llo/hooks/pre-lock would not exist. If it exists, even > when empty, it does not work (E165001: Failed to start)
This is a known bug. A fix is scheduled for Subversion 1.8. With Subversion 1.8 you'll be able to set a new SVNUseUTF8 option in httpd.conf to work around this. See this issue for details: http://subversion.tigris.org/issues/show_bug.cgi?id=2487 Because a new option needed to be added we cannot apply this fix to 1.7, unfortunately. It is an incompatible configuration file format change.
