Ah I was to quick. I tried it again and got a similar error: SSL negotiation failed: SSL error: parse tlsext [exec] svn: PUT von »/repos/asf/!svn/wrk/baca5765-b559-480b-83ce-602151503d4a/logging/site/trunk/docs/log4php/quickstart.html«: SSL negotiation failed: SSL error: parse tlsext (https://svn.apache.org)
Again googling, this is an interesting article: http://serverfault.com/questions/44470/ssl-error-parse-tlsext-on-large-commit-to-svn-via-apache-gentoo I am just wondering why you was able to commit some stuff while I am not. I am using a Mac for my work. SVN version is 1.6.5 I am bit frustrated on this one, if you have more ideas I would appreciate it. Maybe its also worth to ask infrastructure team Cheers + Thanks Christian On Mon, May 3, 2010 at 7:18 AM, Christian Grobmeier <[email protected]> wrote: > Hi, > >> I ran mvn site-deploy on a Ubuntu box that was just upgraded to 10.4, so >> there might be some weirdness due to the switch. > > makes sense, I read similar in the i-net. > >> I was able to run and apparently successfully commit (rev 940360), but I >> was never prompted for a commit message and after the "exec" statement, the >> build hung. > > I see that some images are corrupted (for example the apache logo). I > will try it again from my box... maybe it works on the second try ;-) > > Cheers > Chrstian >
