Re: stupid question (after couple of months with subversion)

Ben Collins-Sussman <sussman@collab.net> writes:

> 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...

I have time for you, of course, but I can't decrypt connection, even
with ssldump(1) and private key.

OTOH, I have tried this on port 80 *without* https. Same problem.

/usr/local/apache2/bin/svn co http://dav.crol.net -d test2

A test2/lala.h

[...]

(mvz){crolvax}[mvz]$ cd test2
(mvz){crolvax}[test2]$ /usr/local/apache2/bin/svn st
(mvz){crolvax}[test2]$ vi lala.h
(mvz){crolvax}[test2]$ /usr/local/apache2/bin/svn st
M ./lala.h
(mvz){crolvax}[test2]$ /usr/local/apache2/bin/svn ci
Sending /home/mvz/test2/lala.h
Committed revision 19.
(mvz){crolvax}[test2]$ /usr/local/apache2/bin/svn st
M ./lala.h

I think we can partialy exclude SSL as bugmaker from this story.

I have trace from session now, Can i send it as attachment on this
list?

-- 
This signature intentionally left blank
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org