You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Mark Hindess <ma...@googlemail.com> on 2008/06/05 12:02:13 UTC
[general] svn up errors?
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.
Re: [general] svn up errors?
Posted by Tony Wu <wu...@gmail.com>.
just googled the web. there is a similar problem that if the filename
in repos contains non-utf8 characters, a request failed w/ 200OK will
come out when using non-secure http. And there is already a defect
ticket here: http://subversion.tigris.org/issues/show_bug.cgi?id=2748.
It would be good to know on which file you encounter this problem.
On Thu, Jun 5, 2008 at 11:23 PM, Alexey Varlamov
<al...@gmail.com> wrote:
> Do we really need to commit it, if single local mod solves the problem for you?
> I mean, there is a reason to have externals imported via http: the
> whole workspace should be fetchable with plain http. Otherwise
> federated build does not do well in clean env, and we had a few
> complaints about that.
> --
> Alexey
>
> 2008/6/5, Oliver Deakin <ol...@googlemail.com>:
>> 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
>>
>>
>
--
Tony Wu
China Software Development Lab, IBM
Re: [general] svn up errors?
Posted by Alexey Varlamov <al...@gmail.com>.
Do we really need to commit it, if single local mod solves the problem for you?
I mean, there is a reason to have externals imported via http: the
whole workspace should be fetchable with plain http. Otherwise
federated build does not do well in clean env, and we had a few
complaints about that.
--
Alexey
2008/6/5, Oliver Deakin <ol...@googlemail.com>:
> 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
>
>
Re: [general] svn up errors?
Posted by Oliver Deakin <ol...@googlemail.com>.
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
Re: [general] svn up errors?
Posted by Regis <xu...@gmail.com>.
Hi,
I meet the same error intermittently. I changed the svn:externals
property to
https just now, no error happens (I run "svn up" five times). But i'm
not sure it's
just intermittently become ok.
Best Regards,
Regis.
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.
>
>
>