Miroslav Zubcic <mvz@crol.net> writes:
> New apache on start says this:
> Apache/2.0.33-dev (Unix) DAV/2 SVN/0.9.0 (rc2) mod_ssl/3.0a0 OpenSSL/0.9.6b
>
> I was thinking - this MUST work, this guys are using it for their
> production, but ...
>
> (maked copy of few random files from apache, added and commited, then
> checkout in another working copy)
>
> (mvz){crolvax}[mvz]$ /usr/local/apache2/bin/svn co https://dav.crol.net -d test1
> mvz's password:
>
> A test1/utils.h
> A test1/regex2.h
> A test1/cclass.h
>
> [... cut ...]
> >
> (mvz){crolvax}[test1]$ /usr/local/apache2/bin/svn ci
> Sending /home/mvz/test1/utils.h
> Committed revision 2.
> (mvz){crolvax}[test1]$ /usr/local/apache2/bin/svn st
> M ./utils.h
>
>
> Argh !!!
>
> I'm willing to try r.1387 or later if you still insist.
>
The only variable that comes to mind is the fact that you're using
SSL. We don't use that in production , and *I* have never tried it
myself. There's obviously something wrong with the 'post-commit'
processing. There are other developers on this list who are using
ssl, no? Can they reproduce the problem?
One thing that might help, Miroslav, is to send us an HTTP trace of
the commit (MERGE) request and the server's response. The server's
response is parsed and used to tweak metadata on the committed
working-copy files. Maybe there's something wrong with the response.
Try tracing the commit with 'ethereal' and sending us the results, if
you have time...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:10 2006