Well, let's try the next logical steps.  Can the svn client on that machine
'svn ls' against the root of that repository?  How about against a
completely different googlecode repository?  How about against some other
svn repository not on googlecode (like http://svn.apache.org/repos/asf/ ) ?

My suspicion is that there's something broken about that machine -- like a
firewall inside it, close to it, etc.


On Fri, Mar 4, 2011 at 11:47 AM, Latif Khalifa <[email protected]>wrote:

> Yes, I get the same error:
>
> $ svn ls
> http://libopenmetaverse.googlecode.com/svn/libopenmetaverse/trunk/
>
> svn: Server sent unexpected return value (403 Forbidden) in response
> to OPTIONS request for
> 'http://libopenmetaverse.googlecode.com/svn/libopenmetaverse/trunk'
>
>
> On Fri, Mar 4, 2011 at 1:43 PM, Ben Collins-Sussman <[email protected]>
> wrote:
> > Sorry, I have no ideas, since the repository is clearly up and working,
> > including that path.  OPTIONS is the very first request an svn client
> sends
> > to a repository when it connects -- a simple read, which never requires
> > authentication.  I'm unable to reproduce the problem.
> > Perhaps it's something specific to that machine?  For example, can you
> run
> > an 'svn ls URL' from the commandline of the TeamCity computer?
> >
> > On Fri, Mar 4, 2011 at 2:27 AM, Latif Khalifa <[email protected]>
> > wrote:
> >>
> >> Hi Ben,
> >>
> >> The same configuration has been working for about two years.
> >>
> >> The actual error it's getting is:
> >>
> >> svn: OPTIONS of '/svn/libopenmetaverse/trunk': 403 Forbidden
> >> (http://libopenmetaverse.googlecode.com)
> >>
> >> So svn OPTIONS on
> >> http://libopenmetaverse.googlecode.com/svn/libopenmetaverse/trunk/ is
> >> failing and that is certainly a valid path.
> >>
> >> Latif
> >>
> >> On Fri, Mar 4, 2011 at 4:45 AM, Ben Collins-Sussman <[email protected]
> >
> >> wrote:
> >> > Um, I don't think this has anything to do with Google Code.  Your
> >> > TeamCity
> >> > config is messed up somehow -- it's trying to read the repository path
> >> > /buildroot/trunk/, and that directory doesn't exist (hence the 403
> >> > error).
> >> >  And as far as I can tell (looking through the repository's history),
> >> > that
> >> > repository path has never existed.
> >> >
> >> > On Thu, Mar 3, 2011 at 6:18 PM, Latif Khalifa <[email protected]
> >
> >> > wrote:
> >> >>
> >> >> Btw. you can see example of failures:
> >> >>
> >> >>
> >> >>
> >> >>
> http://tc.openmetaverse.org/project.html?projectId=project13&tab=projectOverview&guest=1
> >> >>
> >> >>
> >> >>
> http://tc.openmetaverse.org/project.html?projectId=project2&tab=projectOverview&guest=1
> >> >>
> >> >> Latif
> >> >>
> >> >> On Thu, Mar 3, 2011 at 11:25 PM, Latif Khalifa <
> [email protected]>
> >> >> wrote:
> >> >> > Hi,
> >> >> >
> >> >> > We're running continuous integration service for a few opensource
> >> >> > projects using TeamCity from JetBrains. Looks like TeamCity is
> having
> >> >> > trouble contacting subversion repositories at Google Code. It fails
> >> >> > with:
> >> >> >
> >> >> > svn: OPTIONS of '/svn/libopenmetaverse/trunk': 403 Forbidden
> >> >> > (http://libopenmetaverse.googlecode.com)
> >> >> >
> >> >> > I don't know when this problem started, but it is within the last
> >> >> > couple of weeks.
> >> >> >
> >> >>
> >> >> --
> >> >> You received this message because you are subscribed to the Google
> >> >> Groups
> >> >> "Project Hosting on Google Code" group.
> >> >> To post to this group, send email to
> >> >> [email protected].
> >> >> To unsubscribe from this group, send email to
> >> >> [email protected].
> >> >> For more options, visit this group at
> >> >> http://groups.google.com/group/google-code-hosting?hl=en.
> >> >>
> >> >
> >> >
> >
> >
>

-- 
You received this message because you are subscribed to the Google Groups 
"Project Hosting on Google Code" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-code-hosting?hl=en.

Reply via email to