Sometimes it is simply necessary to do a cleanup of the working copy and then
start an update, assuming the check-out got anywhere. These are sometimes
simply synchronization glitches. If the check-out failed completely, I'd delete
that aoo-trunk folder and start over.
Another problem that sometimes happens with check-outs/updates to Windows
computers is the presence of filename characters that are inadmissible on
Windows (or that clash because the Windows file system is not case sensitive by
default). A common case is : in a file path or the ending file name.
I have been needing to do a full trunk check-out as part of paving a new
machine. I just did a full checkout of the trunk HEAD (revision 1490672)
without externals with no problem.
- Dennis
PS: I recommend using TortoiseSVN on Windows 7. It works just fine. If the
command-line svn is being used (as it appears in the error report), there may
be more to figure out. Running in a VM or under CygWin could also complicate
matters.
-Original Message-
From: Oliver-Rainer Wittmann [mailto:orwittm...@googlemail.com]
Sent: Friday, June 7, 2013 01:11 AM
To: dev@openoffice.apache.org
Subject: Re: Error using svn (Building in Win7)
Hi,
On 06.06.2013 19:59, Ivan Fuentes wrote:
I got this error while i was using :
svn co https://svn.apache.org/repos/asf/openoffice/trunk aoo-trunk
svn: E175002: REPORT de '/repos/asf/!svn/me': Could not read response
body: Secure connection truncated (https://svn.apache.org)
How can i continue?
I do not know what went wrong.
But may be it helps to get the repro from
http://svn.apache.org/... - http instead of https
Best regards, Oliver.
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
