On Sun, Dec 27, 2009 at 6:06 PM, Tim Ellison <t.p.ellison_at_gmail.com> wrote:
> On 24/Dec/2009 14:49, Stefan Sperling wrote:
>> On Wed, Dec 23, 2009 at 01:31:36PM +0000, Tim Ellison wrote:
>>> I'm trying to checkout Apache Harmony on an x86_64 machine using the SVN
>>> command-line client 1.6.6 binaries downloaded from CollabNet.
>>> I get the following error (below), which does not occur when I
>>> subsequently update the top level directory using TortoiseSVN.
>>> Trying svn cleanup as advised did not help.
>>> Any suggestions welcome, otherwise I can continue with Tortoise as the
>>> [exec] svn: Your .svn/tmp directory may be missing or corrupt; run
>>> 'svn cle
>>> anup' and try again
>>> [exec] svn: Can't open file
>>> UnsupportedCallbackExceptionTest.java.svn-base': The system cannot find
>>> the path
>> Since you're on Windows, maybe the path is too long for the
>> filesystem? I seem to recall that Windows had ridiculous limitations
>> in that domain.
> Don't think so, as I say, the TortoiseSVN client works ok, so creating
> such files is possible.
There's a fundamental difference in how the svn client and TSVN
operate: TSVN creates all its files with full paths. In that case, the
maximum length of a file name on windows is 65k bytes.
The way the SVN client does it is different: it uses relative paths.
In that scenario the maximum file name length of the relative file
name on Windows is 256 bytes.
Given the above, it could very well be you're looking at the Windows limitation.
Received on 2009-12-27 21:13:11 CET