> -----Original Message-----
> From: Johan Corveleyn [mailto:jcorvel_at_gmail.com]
> Sent: Friday, January 14, 2011 11:35 AM
> To: KARR, DAVID (ATTSI)
> Cc: users_at_subversion.apache.org
> Subject: Re: SVN 1.6.15 checkout fails on particular file
>
> On Fri, Jan 14, 2011 at 7:35 PM, KARR, DAVID (ATTSI) <dk068x_at_att.com>
> wrote:
> > This is a continuation of my experiences described in the "What SVN
> > command-line client distro should I get to work properly with SVN
> 1.4.x
> > on the server?" subject.
> >
> > My SVN server is running version 1.4.x. I'm using the latest
> Subversive
> > in Eclipse, but the connector associated with SVN 1.5.6. This works
> > well enough in Eclipse.
> >
> > I installed SVN 1.6.15 from CollabNet. I created a new directory
> from
> > the shell and did a checkout of two of the projects I have checked
> out
> > in Eclipse. One of them completed successfully, but another one
> fails
> > each time with an error like the following:
> >
> > svn: Your .svn/tmp directory may be missing or corrupt; run 'svn
> > cleanup' and try again
> > svn: Can't open file '...\.svn\tmp\text-base\....svn-base': The
> system
> > cannot find the path specified.
> >
> > I elided the full path to the file.
> >
> > I looked in the "text-base" directory being referenced here, and it's
> > empty.
> >
> > I did a "svn cleanup", and it chugged for a second and then went back
> to
> > the prompt.
> >
> > I tried the checkout again, and it failed with the exact same error.
> >
> > I also tried changing into the directory and doing "svn update", and
> > that also failed with the same error.
> >
> > Any ideas?
>
> Could it be that there are case-clashing filenames in that directory,
> which you are trying to checkout on a case-insensitive filesystem
> (since you are on Windows)?
>
> Perhaps someone committed two files to the repository that only differ
> in case, like readme.txt and README.TXT. If you try to check this out
> on a case-insensitive filesystem, it will fail. You should be able to
> see exactly what's in the repository by running "svn ls $URL".
Hmm. I think I found a big clue. When I do the checkout, I'm giving it an alternate name. The "svn checkout" doc is clear that this is legal. In other words, I'm doing "svn checkout svn:... desiredname".
I've tried doing this several times, and it almost always fails on trying to check out this particular file.
I just tried doing the checkout again, but without the alternate name, and it completed without error.
I then tried changing the checkout to use a "simpler" alternate name. I was using a name like "projectname-branch". I then tried "projectname-a". Both of these fail. If I instead use an alternate name of "a", or "projectname" (using the original project name), or "a-a", those all succeed.
I then tried using an alternate name of "projectnamexx". That fails with the same error.
I then tried "abcdefghijklmnopqr" (actually all the iterations before that), and that succeeds, but "abcdefghijklmnopqrs" (one more letter) fails.
I then looked at the full local path this file would represent, and the entire path is 260 characters long. I would think if there's any threshold, it would be at 255, not 259.
Any idea what's going on here?
>
> Cheers,
> --
> Johan
Received on 2011-01-14 21:20:46 CET