I'm sending this query to users instead of dev first, per the text
suggesting what to do before adding it to the Issue Tracker.
I wanted to set up a specific box to be my svn server for my project, and
had an old alpha (!) lying around that seemed appropriate for the task. A
fresh install of debian stable, and then I compiled svn (0.34), apache
(2.0.48), and berkeleydb (4.0.14), and got everything set up.
I then imported by repository, went though the ssl certificate dance, and
then tried to connect from my client. http works just fine, but https
(using both the debian 0.33 client and a custom-compiled 0.34 client, both
on x86) chokes on some sections of the tree with :
svn: RA layer request failed
svn: REPORT request failed on '/soma/!svn/vcc/default'
svn: REPORT of '/soma/!svn/vcc/default': Could not read response body:
SSL error: illegal padding (https://soma.mit.edu)
It's always on a certain file in the repository, and both http and file://
methods can access it from either platform without problem.
I worried it may have been an openssl issue, since I had compiled things
on the server side against 0.9.6 (this is debian stable, so it's a bit
behind :) ) and the clients were all 0.9.7-compiled.
But upgrading and recompiling on the server didn't help things, I still
get the same error. I even get that error when using the client _on_ the
server, i.e. it doesn't appear to be a strange cross-architecture problem.
Any thoughts? Have people seen this before? I've saved in a text file all
my ./configure parameters, and am willing to let people try and access the
repository to reproduce the bug on their own.
I'm going to be really embarassed if this is another case of me needing to
better RTFM :)
...Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Dec 7 07:32:10 2003