Hm, actually I found a workaround. If I use https instead of http, it works fine. But I think it should also work with http. 2011/6/2 Vampire <Vampire@xxxxxxxxxxxxxxxxxxxxxx>: > It seems to me that this happens while git-svn is searching for history. > As far as I have understood git-svn searches hierarchical higher paths > for history in other places than specified. > I guess while trying to access all those paths some path is tried that > returns 403 Forbidden. > My assumption is that git-svn takes this as cause to abort instead of > ignoring this return state what would be appropriate in this case I > think. > > 2011/6/2 Drew Northup <drew.northup@xxxxxxxxx> >> >> On Thu, 2011-06-02 at 14:22 +0200, Vampire wrote: >> > Drew? >> > >> I have no idea. If anybody else on the list does I'd welcome it, but I >> don't have any more time I can spend on this. >> >> > 2011/4/3 Vampire <Vampire@xxxxxxxxxxxxxxxxxxxxxx> >> > Any news on this one? >> > >> > >> > 2011/2/25 Vampire <Vampire@xxxxxxxxxxxxxxxxxxxxxx> >> > > >> > > I tried it with 1.6.3.3 and with a self-compiled version >> > from latest git code. >> > > >> > > 2011/2/24 Drew Northup <drew.northup@xxxxxxxxx> >> > > > >> > > > On Fri, 2011-02-18 at 15:21 +0100, Vampire wrote: >> > > > > Hi Drew, >> > > > > >> > > > > SVN client is in version 1.6.5. >> > > > > svn co http://svn.apache.org/repos/asf/ant/core/trunk . >> > > > > works fine and without problem. >> > > > > I guess it is in the phase of searching for history in >> > other places in >> > > > > the repository and there some place is accessed that is >> > password >> > > > > protected. >> > > > > I did not contact the server admin as the normal svn >> > client works fine >> > > > > and so it seems to be a problem of git-svn, not of the >> > SVN server. >> > > > > Did you try the command I gave you and does it succeed >> > for you? It is >> > > > > a publicly available repository so you should be able to >> > reproduce the >> > > > > problem. >> > > > > >> > > > > Regards >> > > > > Björn >> > > > >> > > > The error is reproducible, and I'm running a newer >> > subversion client >> > > > than you are. It definitely isn't making it through all of >> > the revisions >> > > > available before dying. >> > > > >> > > > ..... >> > > > Checked through r161300 >> > > > Checked through r161400 >> > > > RA layer request failed: Server sent unexpected return >> > value (403 Forbidden) in response to REPORT request for >> > '/repos/asf/!svn/vcc >> > > > /default' at /usr/libexec/git-core/git-svn line 5131 >> > > > >> > > > I forgot to ask, which version git are you running? I am >> > running 1.7.4 >> > > > on the machine I tried this (RHEL5 RPM, compiled locally). >> > > > >> > > > > 2011/2/18 Drew Northup <drew.northup@xxxxxxxxx>: >> > > > > > >> > > > > > On Mon, 2011-02-14 at 18:24 +0100, Vampire wrote: >> > > > > >> Hi, >> > > > > >> >> > > > > >> I'm trying to issue the following command: >> > > > > >> >> > > > > >> git svn clone --stdlayout >> > http://svn.apache.org/repos/asf/ant/core/ . >> > > > > >> >> > > > > >> But unfortunately this fails after some time with the >> > message: >> > > > > >> >> > > > > >> RA layer request failed: Server sent unexpected >> > return value (403 >> > > > > >> Forbidden) in response to REPORT request for >> > > > > >> '/repos/asf/!svn/vcc/default' >> > at /usr/lib/git-core/git-svn line 4354 >> > > > > >> >> > > > > >> Regards >> > > > > >> Björn >> > > > > > >> > > > > > Björn, >> > > > > > Have you made sure your subversion client is >> > up-to-date? Does this work >> > > > > > as a plain svn clone? Have you contacted the server >> > admin? >> > > > > > Without context we cannot act on this. >> > > > > > >> > > > >> > > > -- >> > > > -Drew Northup >> > > > ________________________________________________ >> > > > "As opposed to vegetable or mineral error?" >> > > > -John Pescatore, SANS NewsBites Vol. 12 Num. 59 >> > > > >> > >> >> -- >> -Drew Northup >> ________________________________________________ >> "As opposed to vegetable or mineral error?" >> -John Pescatore, SANS NewsBites Vol. 12 Num. 59 >> > -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html