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

Bug in svn: protocol involving spaces (Modified by Stuart A. Malone)

From: Stuart A. Malone <samalone_at_llamagraphics.com>
Date: 2004-07-29 17:26:16 CEST

Marcos Chaves on the users mailing list was able to reproduce this bug,
and neither of us can find it in the issue tracker database, so I
thought it was time to bring this up on the dev mailing list:

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.

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

Received on Fri Jul 30 14:48:52 2004

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.