Repository files with illegal Windows filenames generate cryptic error messages

I ran into the follwing issue today:
After a developer in a linux environemtn committed a new file with a colon
character in it (for example: "illegal:name.txt"), the next update using
TSVN generated the following error:

Error: Can't open file
'C:\WorkingCopy\test\.svn\tmp\text-base\illegal:name.txt':
The parameter is incorrect.

Before I discovered that the filename was the culprit (it may have been
obvious to others) :-), I attempted to clean my working copy, which in
turn generated an error message about my working copy being "locked".
(An unlock did not fix the issue either)

Eventually I used the TSVN Repo-Browser to rename the offending file,
which fixed the issue.

But here are my suggestions/requests:
- Could the update make sure that each file is "windows-legal' before
trying to update it? (Perhaps even offering the chance to ignore it)
- If not, could the error message be improved?
- Or is this an SVN issue, unrelated to TSVN?

Thanks,

My TSVN info:
TortoiseSVN 1.3.3, Build 6219 - 32 Bit
Subversion 1.3.1,
apr 0.9.7
apr-iconv 0.9.7
apr-utils 0.9.7
berkeley db 4.3.28
neon 0.25.4
OpenSSL 0.9.8a 11 Oct 2005
zlib 1.2.3

(I'm using Windows Xp Pro, Service Pack 2)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Tue Apr 11 04:40:14 2006