Hi,
I'm installing from the fedora rpm's, and the corresponding download
server set up for svn at
http://summersoft.fay.ar.us/pub/subversion/latest/fedora/bin/
I suspected mixed binaries, so I explicitly did a rpm -e for the
subversion packages, and verified that mod_dav_svn and libsvn_fs had
been removed. I then re-installed 0.37.
Is there anything specific you would like me to look for? Are there any
other ways of testing remote connections? Local connections seem to work
fine. I tried:
svnlook info /var/vc /
and got back 0. I suppose this would be expected for a new repository?
Sunil
Ben Collins-Sussman wrote:
> On Sun, 2004-02-08 at 22:32, Toshio wrote:
>
>
>>On Sun, 2004-02-08 at 16:49, smishra@speakeasy.net wrote:
>>
>>>>To recap, I entirely removed my previous subversion installation,
>>>>then
>>>>installed 0.37. I created a brand new repository, and tried
>>>>connecting
>>
>>I had something similar happen to me the other day. It was because I
>>forgot to restart apache. Even though the new mod_dav_svn is in the
>>filesystem, the httpd thread you're accessing might still have the old
>>one loaded into memory.
>
>
> This would cause the *opposite* problem: you'd have a 0.33 mod_dav_svn
> trying to read a 0.37 repository. It would expect schema '2' but find
> schema '3' instead.
>
> The error message expected '3' but found '2'. Somehow, this indicates
> to me that mod_dav_svn is definitely version 0.37, but that somehow you
> used a 0.33 'svnadmin' to create your repository.
>
> I'm guessing you still have mixed libraries on your system from two
> different versions, or perhaps mixed binaries lying aound.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 9 06:01:11 2004