* Daniel Shahaf :
> Presumably, tcpdump/wireshark of the response headers will be useful.
The problem was very subtle:
Apache delivered a P3P header (our own configuration). This broke the checkout.
Why only a certain file was affected (it worked when the file was not in the
repo) or why it worke
Hi,
answering my own post:
* Fridtjof Busse :
>
> The httpd process starts consuming up to 4GB and then dies, killing the
> svn client process with:
> svn: REPORT of '/svn/prod/!svn/vcc/default': Could not read chunk size:
> connection was closed by server
Set
Hi,
we're running a SVN repo (~6GB) on 1.7.3.
Checking out the entire repo in one "svn co" (both 1.6 and 1.7) session is
almost impossible.
The httpd process starts consuming up to 4GB and then dies, killing the svn
client process with:
svn: REPORT of '/svn/prod/!svn/vcc/default': Could not read
dereferences the symlink
> when it shouldn't or didn't, so I don't think this is related to #4091.
>
> Could you file a new issue for this? And, if possible, provide
> a reproduction script.
>
> Thanks,
>
> Daniel
>
>
> Fridtjof Busse wrote on Thu
Hi,
we've started to test Subversion 1.7.3 on linux and noticed a somewhat drastaic
change in svn behavior.
Our repo (also 1.7, a svnsync copy) contains a lot of symlinks and externals.
Different from Subversion 1.6, every one of those symlinks shows up as "M" in
"svn status".
"svn diff" chokes
