From: Vampire <Vampire@Masters-of-Disaster.de>
To: Drew Northup <drew.northup@maine.edu>
Cc: git@vger.kernel.org
Subject: Re: git svn clone failing
Date: Fri, 25 Feb 2011 01:44:21 +0100 [thread overview]
Message-ID: <AANLkTikA2iRWH8Bh16CmpFpACSOjCiqc3c9cU69Jduv3@mail.gmail.com> (raw)
In-Reply-To: <1298587459.22431.19.camel@drew-northup.unet.maine.edu>
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@maine.edu>
>
> 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@maine.edu>:
> > >
> > > 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
>
next prev parent reply other threads:[~2011-02-25 0:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 17:24 git svn clone failing Vampire
2011-02-18 12:56 ` Drew Northup
2011-02-18 14:21 ` Vampire
2011-02-24 22:44 ` Drew Northup
2011-02-25 0:44 ` Vampire [this message]
2011-04-03 0:21 ` Vampire
[not found] ` <BANLkTin7bxu_XZVYaVy+eXuhcJR83hXSew@mail.gmail.com>
2011-06-02 12:55 ` Drew Northup
2011-06-02 14:51 ` Vampire
2011-06-02 17:48 ` Vampire
2011-06-28 4:28 ` Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTikA2iRWH8Bh16CmpFpACSOjCiqc3c9cU69Jduv3@mail.gmail.com \
--to=vampire@masters-of-disaster.de \
--cc=drew.northup@maine.edu \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).