If anybody cares...<br>
<br>
My local subversion install failed to compile some of its libraries
because it was missing dependencies. But because it reported this as a
warning instead of an error, I didn't notice it. (Arguably, since those
libraries are crucial for the app to actually <span style="font-weight: bold;">do</span>
anything, perhaps it should have been an error.) When my local binary
couldn't find its libraries, it proceeded down the library path and
found the server install, which was producing the version mismatch. <br>
<br>
Fixed the dependencies, and all was well! <br><br><br><div><span class="gmail_quote">On 2/16/07, <b class="gmail_sendername">Shane Liesegang</b> <<a href="mailto:shane@shaneliesegang.com">shane@shaneliesegang.com</a>> wrote:
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">OK, upon further inspection...<br><br>SVN is compiled and installed local to my user account. But
when I go to run it, it's apparently still looking at the global
libraries, which are a different version. I've tried setting
LD_LIBRARY_PATH, but it still gives me the same error. <br><br>I want to use ldd to see which libraries it's actually trying
to load, but it'll only let me do that on the vanilla executable. That
is, I can "ldd ~/bin/svn" and get it's libraries (which all point to
the proper versions), but the problem arises when I try to do something
with svn, like update or commit. Heck, even "svn help" throws an error.
But I can't find a way to make ldd run on a program with command line
arguments; it treats anything space separated as a different executable
it's supposed to test. My guess is that SVN doesn't actually load the libraries until it tries to do something, and at that point it's looking in the wrong place. <br><br>Oh, such convoluted issues. Anybody have any thoughts? This is making me sad.
<div><span class="e" id="q_110ccd00e1e9dcdf_1"><br><br><br><br><div><span class="gmail_quote">On 2/16/07, <b class="gmail_sendername">Shane Liesegang</b> <<a href="mailto:shane@shaneliesegang.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
shane@shaneliesegang.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hmmm. I figured I might have to match the repository, but I'm getting the error without ever even trying to connect to anything (svn help). Which leads me to think there's some kind of program config problem I need to deal with before even trying to connect to a repo.
<br><br>Curiouser and curiouser... <div><span><br><br><br><div><span class="gmail_quote">On 2/16/07, <b class="gmail_sendername">Weber, Lawrence A</b> <<a href="mailto:laweber@switch.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
laweber@switch.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial" size="2">A few months ago, I tried to convert our Version Control to
SVN. In the middle of my eval tests, SVN was upgraded resulting in my
TortoiseSVN client being a newer than my command line tools. I
used the command line tools to create my repositories but planned to provide the
users with TortoiseSVN. When I used the newer TortoiseSVN it changed
the repository format so that the command line client could no longer access
files. Same kind of errors you are seeing. This feature caused so
much trouble that I was forced to ClearCase, yuck.</font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial" size="2"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial" size="2">Looks like you need to get the older client. One that
matches your repository.</font></span></div>
<blockquote style="margin-right: 0px;">
<div dir="ltr" align="left" lang="en-us">
<hr>
<font face="Tahoma" size="2"><b>From:</b>
wplug-bounces+laweber=<a href="mailto:switch.com@wplug.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">switch.com@wplug.org</a>
[mailto:<a href="mailto:wplug-bounces+laweber=switch.com@wplug.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">wplug-bounces+laweber=switch.com@wplug.org</a>] <b>On Behalf Of </b>Shane
Liesegang<br><b>Sent:</b> Friday, February 16, 2007 2:04 PM<br><b>To:</b>
General user list<br><b>Subject:</b> [wplug] SVN upgrade -> mismatched RA
version<br></font><br></div><div><span>
<div></div>I'm on a shared host that uses version 1.3.2 of Subversion, and I
recently compiled and installed a local copy of version 1.4.3. <br><br>Now
when I try to run any svn commands, I get a message about mismatched RA
versions. <br><br>$ svn help<br>svn: Mismatched RA version for 'dav': found
1.4.3, expected 1.3.2<br>$ svn co http://{my_repo}<br>svn: Mismatched RA
version for 'http': found 1.4.3, expected 1.3.2<br><br><br>Some googling
showed that these errors happen when there's bits of old installs leftover
from an upgrade. Of course, in my case, the old version is still on the
system. I get these even if I directly run the new binary (as opposed to
trusting my $PATH). <br><br>Has anybody dealt with this before? Any words of
advice on how to proceed? I'm afraid I hosed SVN. :-(
<br></span></div></blockquote></div>
</blockquote></div><br>
</span></div></blockquote></div><br>
</span></div></blockquote></div><br>