[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn lock fails if filename contains special character (utf8)

From: Stefan Sperling <stsp_at_elego.de>
Date: Fri, 12 Oct 2012 01:24:40 +0200

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_at_sv1 [/home/naox]# cd test
> naox_at_sv1 [/home/naox/test]# touch file1
> naox_at_sv1 [/home/naox/test]# touch file2ząb
> naox_at_sv1 [/home/naox/test]# svn add file1
> A file1
> naox_at_sv1 [/home/naox/test]# svn add file2ząb
> A file2ząb
> naox_at_sv1 [/home/naox/test]# svn commit
> Dodawanie file1
> Dodawanie file2ząb
> Przesyłanie treści pliku..
> Committed revision 1.
> naox_at_sv1 [/home/naox/test]# svn lock file1
> 'file1' zablokowane przez użytkownika 'test'.
> naox_at_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:

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.
Received on 2012-10-12 01:25:14 CEST

This is an archived mail posted to the Subversion Dev mailing list.