svn client issues (Was: xml-fop Build Failed)

[David Crossley <cr...@apache.org>]

Clay Leeds wrote:
> As if I didn't have enough worries with this, I'm having problems with 
> SVN:
> 
> svn: REPORT request failed on '/repos/asf/!svn/vcc/default'
> svn: REPORT of '/repos/asf/!svn/vcc/default': 400 Bad Request 
> (http://svn.apache.org)
> 
> Process finished with exit status 1.
> 
> Anyone have an idea how I can resolve this? Is this on my end, or is it 
> a problem with svn.apache.org?

There is no problem for me at the moment.
You would need to provide us with more info.
Are you trying to do svn checkout or svn update or ...?

Google found some stuff about your issue. I don't know
if this is relevant but here is one snippet:
"Doh!  It turns out my isp is running a proxy that breaks subversion."

-- 
David Crossley

Re: svn client issues (Was: xml-fop Build Failed)

[Clay Leeds <cl...@medata.com>]

On Aug 2, 2004, at 3:40 PM, David Crossley wrote:
> Clay Leeds wrote:
>> ...Before
>> I 'bother' the folks at erm... wherever I have to ask 
>> (infrastructure@?
>> they haven't updated the Committers FAQ to include SVN yet), I'll ask
>> here: ...
>
> http://www.apache.org/dev/version-control.html
>
> -- 
> David Crossley

Thanks but I've 'been there, done^H^H^H^Hread that'. :-) Although 
there's a topic 'Problems with Subversion?' it only references a 
particular problem & solution (nothing related to my issue) and doesn't 
indicate:

- that anyone has access over https (it only references COMMITTERS)
- who to ask for help for *svn* (they've got a contact for CVS)

When i said "didn't include SVN" I guess I should've been clearer that 
I went to that page but didn't find what I was looking for.

Web Maestro Clay

p.s. [OT] I'm at home now, so I shouldn't have to worry about any of 
this 'til I get back to work tomorrow... Of course, in the meantime I 
updated to the svn-ssl version and now it doesn't work at all, but 
that's a different issue for a different list!

Re: svn client issues (Was: xml-fop Build Failed)

[David Crossley <cr...@apache.org>]

Clay Leeds wrote:
> ...Before 
> I 'bother' the folks at erm... wherever I have to ask (infrastructure@? 
> they haven't updated the Committers FAQ to include SVN yet), I'll ask 
> here: ...

http://www.apache.org/dev/version-control.html

-- 
David Crossley

Re: svn client issues (Was: xml-fop Build Failed)

[Dave Brondsema <da...@brondsema.net>]

On Mon, 2 Aug 2004, Clay Leeds wrote:

> On Jul 30, 2004, at 6:51 PM, David Crossley wrote:
> > Clay Leeds wrote:
> >> As if I didn't have enough worries with this, I'm having problems with
> >> SVN:
> >>
> >> svn: REPORT request failed on '/repos/asf/!svn/vcc/default'
> >> svn: REPORT of '/repos/asf/!svn/vcc/default': 400 Bad Request
> >> (http://svn.apache.org)
> >>
> >> Process finished with exit status 1.
> >>
> >> Anyone have an idea how I can resolve this? Is this on my end, or is
> >> it
> >> a problem with svn.apache.org?
> >
> > There is no problem for me at the moment.
> > You would need to provide us with more info.
> > Are you trying to do svn checkout or svn update or ...?
> >
> > Google found some stuff about your issue. I don't know
> > if this is relevant but here is one snippet:
> > "Doh!  It turns out my isp is running a proxy that breaks subversion."
> >
> > --
> > David Crossley
>
> Although it works nicely from home, I'm actually still getting errors
> from work. It looks like my sysadmin doesn't want us to do this type of
> POST over HTTP. If I can change it to HTTPS I think I'll be OK. Before
> I 'bother' the folks at erm... wherever I have to ask (infrastructure@?
> they haven't updated the Committers FAQ to include SVN yet), I'll ask
> here: Does my xml-fop COMMITTER status enable me to use svn over HTTPS
> for forrest?
>
> On a whim, I tried it with a 'new' repos, but I get an error:
>
> [clay@Clays-TiBook cvs_stuff]$ svn co
> https://svn.apache.org/repos/asf/forrest/trunk forrest_https
> svn: Unrecognized URL scheme
> 'https://svn.apache.org/repos/asf/forrest/trunk'
> [clay@Clays-TiBook cvs_stuff]$
>

Anybody can use https instead of http, but it's required for committers.

Looks like your svn binary doesn't have https support compiled in.  See if
svn --version says anything about the https schema.

I too occasionally have problems behind a proxy.  Sometimes I have to do a
new checkout when an update fails.  Look to the SVN book at
http://svnbook.red-bean.com/ for details on proxy configuration.

-- 
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
http://csx.calvin.edu : student org

Re: svn client issues (Was: xml-fop Build Failed)

[Clay Leeds <cl...@medata.com>]

On Jul 30, 2004, at 6:51 PM, David Crossley wrote:
> Clay Leeds wrote:
>> As if I didn't have enough worries with this, I'm having problems with
>> SVN:
>>
>> svn: REPORT request failed on '/repos/asf/!svn/vcc/default'
>> svn: REPORT of '/repos/asf/!svn/vcc/default': 400 Bad Request
>> (http://svn.apache.org)
>>
>> Process finished with exit status 1.
>>
>> Anyone have an idea how I can resolve this? Is this on my end, or is 
>> it
>> a problem with svn.apache.org?
>
> There is no problem for me at the moment.
> You would need to provide us with more info.
> Are you trying to do svn checkout or svn update or ...?
>
> Google found some stuff about your issue. I don't know
> if this is relevant but here is one snippet:
> "Doh!  It turns out my isp is running a proxy that breaks subversion."
>
> -- 
> David Crossley

Although it works nicely from home, I'm actually still getting errors 
from work. It looks like my sysadmin doesn't want us to do this type of 
POST over HTTP. If I can change it to HTTPS I think I'll be OK. Before 
I 'bother' the folks at erm... wherever I have to ask (infrastructure@? 
they haven't updated the Committers FAQ to include SVN yet), I'll ask 
here: Does my xml-fop COMMITTER status enable me to use svn over HTTPS 
for forrest?

On a whim, I tried it with a 'new' repos, but I get an error:

[clay@Clays-TiBook cvs_stuff]$ svn co 
https://svn.apache.org/repos/asf/forrest/trunk forrest_https
svn: Unrecognized URL scheme 
'https://svn.apache.org/repos/asf/forrest/trunk'
[clay@Clays-TiBook cvs_stuff]$

Thanks

Re: svn client issues (Was: xml-fop Build Failed)

[Clay Leeds <cl...@medata.com>]

Thanks for the clue. I just got home from work, and tried the command 
again:

svn co http://svn.apache.org/repos/asf/forrest/trunk forrest

and it's working great. Looks like it was probably a proxy issue from 
my work.

Case closed!

Web Maestro Clay

p.s. D'oh! ;-)

On Jul 30, 2004, at 6:51 PM, David Crossley wrote:
> Clay Leeds wrote:
>> As if I didn't have enough worries with this, I'm having problems with
>> SVN:
>>
>> svn: REPORT request failed on '/repos/asf/!svn/vcc/default'
>> svn: REPORT of '/repos/asf/!svn/vcc/default': 400 Bad Request
>> (http://svn.apache.org)
>>
>> Process finished with exit status 1.
>>
>> Anyone have an idea how I can resolve this? Is this on my end, or is 
>> it
>> a problem with svn.apache.org?
>
> There is no problem for me at the moment.
> You would need to provide us with more info.
> Are you trying to do svn checkout or svn update or ...?
>
> Google found some stuff about your issue. I don't know
> if this is relevant but here is one snippet:
> "Doh!  It turns out my isp is running a proxy that breaks subversion."
>
> -- 
> David Crossley
>