"David Glasser" <firstname.lastname@example.org> writes:
> Could Karl be using http:// instead of https:// by accident?
I had several problems, and it's not clear whether they were related.
But the main one was that I couldn't commit to SVN's *own* repository,
which uses http:// not https://. It's still failing for me:
$ svn st -q
$ svn ci -F msg
svn: Commit failed (details follow):
svn: Server sent unexpected return value (403 Forbidden)
in response to MKACTIVITY request for
$ svn info | grep URL
> Karl's getting the classic "oh noes, I'm behind a stupid http proxy
> that blocks dav requests" error.
Hmmm. Well, there are only two Net connections in my life this week.
One was a cable in the same room with you in downtown Chicago :-), and
the other is the home DSL line in my parents' house.
I've made other commits (r27948, r27932, r27910) successfully this
week, and those must have been over one, or possibly both, of those
connections. I don't remember which one specifically, but the
previously reported failure was definitely from downtown, whereas the
one above is from my parents' house. So, by the pigeonhole principle,
at least one location was formerly successful and now fails; and
possibly this is true of both locations.
(Note to cmpilato: I think that's an example of when it's okay to use
"and" after a semicolon. Finally! Been looking for one of those.)
I've never had this problem before, from either location. If there's
a proxy involved, it's new.
If I still can't commit when I get back to San Francisco and my home
Net connection, I'll try to get on IRC at the same time as someone
with admin privs on svn.collab.net, and we can watch the logs in
real-time while I attempt the commits.
In the meantime, I guess I'll post patches to the list.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Nov 23 04:25:34 2007