Hi Erik,
Thanks for your kindly reply.
It may not be the problem of APR for I tried to compile the latest APR
(1.2.x) with SVN and the same error occured.
I guess there is nothing to do with absolute or relative paths. I
checkouted the repository using the command like this:
svn co https://aaa.bbb.ccc/aaa/bbb/ccc
or
svn up https://....
Best regards!
Sincerely,
Alex Zhu
Quality Engineering Department III
Sunnorth Electronic Technology Co., Ltd.
Tel: +86-10-62981668 Ext. 2792 (Office) / 2056 (3G Lab)
Fax: +86-10-62985972
Email: bohao@sunnorth.com.cn
"Erik Huelsmann" <ehuels@gmail.com> 亟噐 2007-11-24 17:52:51:
> On Nov 24, 2007 4:12 AM, 幀鴎裟 <bohao@sunnorth.com.cn> wrote:
> >
> > Hi George,
> >
> > So this is the problem of the differences of APRs between SVN and
> > TortoiseSVN ?
> >
> > What can we for fixing this issue? Rebuild SVN using the latest APR?
>
> Well, there's another possibility: that this isn't caused by APR;
> TSVN may have been built against the same or another version of APR,
> but may not have. TSVN uses a different compiler for their builds than
> the svn teams uses. This may explain the difference in size and
> checksum for the builds.
>
> There is a significant difference in how svn and TSVN use the windows
> APIs though: TSVN uses absolute paths, which - when handled through
> APR - may be 65k characters long. Presumably, you used relative paths
> with svn. This limits the path name length to (I think) 255 - even
> when handled through APR.
>
> Given that - for its working copy administration - may add
> .svn/tmp/text-base/ to the path name and .svn-base or even .svn-revert
> to the file name, the actual limit on relative paths in svn is much
> shorter than 255.
>
> The workaround would be to use absolute paths like this:
>
> svn update \path\to\very\deep\working\copy
>
>
> HTH,
>
>
> Erik.
Received on Mon Nov 26 04:15:01 2007