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

RE: broken file name handling

From: Paul Charlton <techguru_at_byiq.com>
Date: Tue, 30 Sep 2008 10:13:19 -0700


Thanks for researching that ... but it does not explain how the bad name
ever got into the Windows working copy. We started with an empty working
copy, and simply did "svn co URL/" to create the wc from the remote repo.
At some point, the "svn co" failed with the error noted below, and ever
after the "svn up" reproduces the same message. The behavior is different
(and correct) if you begin with "svn co URL/mk.xiv/" ... (ie: checkout
project vs checkout root)

The undesired behavior is totally reproducible on the SVN repository itself
and was pointed out to me by a colleague.

-----Original Message-----
From: Karl Fogel [mailto:kfogel_at_red-bean.com]
Sent: Tuesday, September 30, 2008 8:57 AM
To: Paul Charlton
Cc: dev_at_subversion.tigris.org
Subject: Re: broken file name handling

"Paul Charlton" <techguru_at_byiq.com> writes:
> "svn up" from http://svn.collab.net/repos/svn/mk.xiv fails from
> windows clients (1.5 collab.net & tortoise) as follows:
> svn: Can't check path '?WHAT?.txt': The filename, directory name, or
> label syntax is incorrect.
> the repo browser shows "-WHAT-.txt"
> It seems like the client and server don't agree on a canonical form for
> filenames which may be incompatible with the underlying client file
> Obviously in the short term, the problem can be fixed by renaming the file
> this project's repository.
> a) I would appreciate a sanity check from a developer experienced with
> project

It looks like renaming is exactly what happened, in r28723:

   r28723 | brane | 2008-01-02 15:13:51 -0500 (Wed, 02 Jan 2008) | 1 line
   Changed paths:
      A /mk.xiv/-WHAT-.txt (from /mk.xiv/?WHAT?.txt:28722)
      D /mk.xiv/?WHAT?.txt
   * mk.xiv/-WHAT-.txt: Renamed from ?WHAT?.txt so it can be read on

The reason your 'update' failed on Windows is because you still have the
old filename (somehow), and Subversion is trying to access that path as
part of changing its name, as part of the update.

If there's a bug here, it's that we created a file (during checkout) on
Windows that we can't later update. The solution would be to not create
it in the first place, but to error instead, perhaps. In the meantime,
you could work around this by just removing the directory and
re-updating, I think. (I don't have a Windows box to test with.)


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-09-30 19:13:33 CEST

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.