Bug in svn: protocol involving spaces

["Stuart A. Malone" <sa...@llamagraphics.com>]

I believe that I have tracked down and can reproduce a problem in 
subversion 1.0.6 involving the way the svn: protocol handles spaces in 
pathnames.  I have found places where issuing a diff or merge command 
remotely using the svn: protocol will fail, where the same command 
issued locally using the file: protocol will succeed.

For example, if I run this command directly on the subversion server, 
it succeeds:

svn diff -r 1226:1193 file:///svnrepos/trunk/Projects/Life%20Balance

But if I run the equivalent command on the same repository from a 
client machine, it fails:

svn diff -r 1226:1193 svn://whirlwind/trunk/Projects/Life%20Balance
svn: Invalid editor anchoring; at least one of the input paths is not a 
directory and there was no source entry

If I do a diff directly on the Projects directory (leaving out 
"/Life%20Balance"), it succeeds on both machines.

Attached is a csh script that reproduces the error.  Edit the 
repository variable at the top of the script to point to a writable 
repository that uses the svn: protocol.

--Stuart A. Malone
   Llamagraphics, Inc.

Re: Bug in svn: protocol involving spaces

[Ben Collins-Sussman <su...@collab.net>]

On Thu, 2004-07-29 at 10:26, Stuart A. Malone wrote:

> svn diff -r 1226:1193 svn://whirlwind/trunk/Projects/Life%20Balance
> svn: Invalid editor anchoring; at least one of the input paths is not a 
> directory and there was no source entry
> 
> If I do a diff directly on the Projects directory (leaving out 
> "/Life%20Balance"), it succeeds on both machines.

Thanks for the csh script.  What an excellent reproduction recipe!

I think that this bug is fixed in svn 1.1;  in fact, I just ran your
script with 1.1 code and sure enough, the bug doesn't reproduce anymore.




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org