I see a similar thing, with regular failures updating concurrent. Oddly
it seems to be fine when there are no or only minimal classlib updates,
but fails if there are longer updates beforehand. No idea why this would
make a difference! If either of the solutions you propose fixes the
problem, then I'm +1 for it.
Regards,
Oliver
Mark Hindess wrote:
Frequently I see errors when running "svn up" in classlib/trunk where
the classlib up works but the concurrent external fails with:
Fetching external item into 'modules/concurrent/standard'
svn: REPORT request failed on '/repos/asf/!svn/vcc/default'
svn: REPORT of '/repos/asf/!svn/vcc/default': 200 OK (http://svn.apache.org)
Anyone else noticed this or is it just me? Anyone any idea why? I'm
not really sure when it started happening but it has been doing it for
quite a while now. It would be good to fix it - perhaps by changing the
external to use https or maybe the new svn.eu.apache.org server.
Regards,
-Mark.
--
Oliver Deakin
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
