I have upgraded to svn 1.2.0 (I realize this is slightly old but a
package was conveniently available and I don't think this difference
is affecting me). Locking works when using the svn+ssh:// or file://
transports. But locking fails for me when using https://. The
message I see is the following, with my url munged.
svn lock foo
svn: Lock request failed: 405 Method Not Allowed (https://example.com)
Because I know that locking works using two of the three methods I
know that svn itself is okay for locking. Or at least I believe so.
But I must be missing a component upgrade in the https:// path that is
needed to support this. But I don't know what. Or perhaps when this
svn was built the autodetection somewhere along the way did not
configure this in. I am stuck. Any hints?
Thanks
Bob
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 29 02:19:33 2005