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

Re: wcprops not updated on commit when entries has UTF-8 chars in repository URL

From: Hiroharu Tamaru <tamaru_at_myn.rcast.u-tokyo.ac.jp>
Date: 2005-05-12 15:10:06 CEST

Thank you, Stefan and Peter for your quick answers

At Thu, 12 May 2005 13:41:25 +0200, SteveKing wrote:

> Try absolute/full paths with the CL client instead of relative paths. If
> then the CL client doesn't escape correctly either, then it's a
> Subversion issue, otherwise a TSVN one.

OK. Command line client escapes URI in .svn/entries

At Thu, 12 May 2005 14:00:46 +0200 (CEST), Peter N. Lundblad wrote:

> > If a .svn/entries file have a repository URL that has RAW
> > (as opposed to %-escaped) utf-8 characters within it, a
> > commit of a file does not update the revision number that
> > appears in the files in .svn/wcprops/* .
> >
> Non-ASCII characters are not allowed in a URI, so there is a bug if
> something lets such characters in. My guess is that something strips the
> repository root part from an URL and getting it wrong since the
> %-escapings don't match. (We have had similar bugs before.)

OK. That's reasonable.

> > Should subversion be more gracefull and process the raw
> > utf-8 url correctly, or should TortoiseSVN be more strict
> > and always %-escape every non-ASCII chars?
> >
> I don't think we should handle this situation, but maybe we should find
> some way to error out, so it gets noticed earlier. I don't know enough
> about how DAV handles wcprop to give a good answer here.

OK. I'm convinced that TortoiseSVN should be fixed.
I'll try their list.

Thank you for your help.

-- 
Hiroharu Tamaru
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 12 15:11:45 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.