subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benjamin Fritz <>
Subject Re: Cannot checkout or clean up using 1.9 dev build
Date Mon, 27 Apr 2015 18:35:49 GMT
Apparently I'm not subscribed to get list emails; please CC me on future
responses. I had to get this message from the archive :-)

Branko ─îibej wrote:
> On 27.04.2015 18:06, Benjamin Fritz wrote:
> > I get the following error when I try to check out a working copy from
> > my repository at work (exact path names obfuscated but length
> > unchanged, in case it matters
> It probably does matter ... FWIW, I believe you did change the length of
> the file name, the workqueue record says 234 chars but the name in the
> record is 240; still, that shouldn't be an issue.

Oops. You're right. My actual directory has only 3 characters where I
replaced with "Prog" in the path string. Still, those 6 fewer
characters are probably irrelevant.

> > ), leaving a partially downloaded working copy:
> >
> > svn: E155009: Failed to run the WC DB work queue associated with
> > 'C:\Project_Files\Proj_Dev\Prog_svn_1.9_cmdline', work item 2160
> > (file-install 234
> >
> > 1 0 1 1)
> > svn: E720123: The filename, directory name, or volume label syntax is
> > incorrect.
> The full path of the file would be 281 characters long, which is more
> than Windows' limit of 260. But Subversion goes to a lot of trouble to
> avoid the path limit ... I wonder what's going on here.
> > I get the same error message when I try "svn cleanup" in this partial
> > working copy.
> >
> > In case it's not clear, I get this error when running the command-line
> > tools (in addition to the TortoiseSVN GUI), so I know it's not
> > something introduced by the TortoiseSVN folks.
> >
> > Is there more detail I can gather to help resolve this, or should I
> > just sit and wait and hope it gets fixed before 1.9 gets released?
> It would really help if you could get a debug-enabled build of the
> command-line tools and try with that, because it'll show the actual
> location where the error is generated. That'll make the problem a bit
> easier to track down.
> By the way, I assume that this all works with 1.8?

Yes, checking out to a similar path using SVN 1.7 or 1.8 (with 1.8 or
1.7 substituted in the working copy path) succeeds without this error
and gives me a full working copy (minus some badly defined externals
left over from 1.6).

Do I need to compile my own SVN to get a debug-enabled build? I
downloaded the source code archive for 1.9 beta, but did not try
compiling yet, due to the large number of dependencies listed in the
INSTALL file. But it looks like there should be a "dependencies zip
file" available, so maybe I'll try that later.

Assuming I get a debug-enabled build, what would I need to do to get the
information needed?

View raw message