It was just the libraries not matching the binary I was using. The repository was fine. :-)<br><br><br><br><div><span class="gmail_quote">On 2/17/07, <b class="gmail_sendername">Michael Semcheski</b> <<a href="mailto:lists@immuneit.com">
lists@immuneit.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;">So just for everyone following keeping score at home, was your
<br>repository ever in danger, or was it just that the binaries had<br>mismatched library versions?<br><br>Mike<br><br>Shane Liesegang wrote:<br>> If anybody cares...<br>><br>> My local subversion install failed to compile some of its libraries
<br>> because it was missing dependencies. But because it reported this as a<br>> warning instead of an error, I didn't notice it. (Arguably, since<br>> those libraries are crucial for the app to actually do anything,
<br>> perhaps it should have been an error.) When my local binary couldn't<br>> find its libraries, it proceeded down the library path and found the<br>> server install, which was producing the version mismatch.
<br>><br>> Fixed the dependencies, and all was well!<br>><br>><br>> On 2/16/07, *Shane Liesegang* <<a href="mailto:shane@shaneliesegang.com">shane@shaneliesegang.com</a><br>> <mailto:<a href="mailto:shane@shaneliesegang.com">
shane@shaneliesegang.com</a>>> wrote:<br>><br>> OK, upon further inspection...<br>><br>> SVN is compiled and installed local to my user account. But when I<br>> go to run it, it's apparently still looking at the global
<br>> libraries, which are a different version. I've tried setting<br>> 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
<br>> load, but it'll only let me do that on the vanilla executable.<br>> That is, I can "ldd ~/bin/svn" and get it's libraries (which all<br>> point to the proper versions), but the problem arises when I try
<br>> to do something with svn, like update or commit. Heck, even "svn<br>> help" throws an error. But I can't find a way to make ldd run on a<br>> program with command line arguments; it treats anything space
<br>> separated as a different executable it's supposed to test. My<br>> guess is that SVN doesn't actually load the libraries until it<br>> tries to do something, and at that point it's looking in the wrong
<br>> place.<br>><br>> Oh, such convoluted issues. Anybody have any thoughts? This is<br>> making me sad.<br>><br>><br>><br>><br>> On 2/16/07, *Shane Liesegang* < <a href="mailto:shane@shaneliesegang.com">
shane@shaneliesegang.com</a><br>> <mailto:<a href="mailto:shane@shaneliesegang.com">shane@shaneliesegang.com</a>>> wrote:<br>><br>> Hmmm. I figured I might have to match the repository, but I'm
<br>> getting the error without ever even trying to connect to<br>> anything (svn help). Which leads me to think there's some kind<br>> of program config problem I need to deal with before even
<br>> trying to connect to a repo.<br>><br>> Curiouser and curiouser...<br>><br>><br>><br>> On 2/16/07, *Weber, Lawrence A* < <a href="mailto:laweber@switch.com">laweber@switch.com
</a><br>> <mailto:<a href="mailto:laweber@switch.com">laweber@switch.com</a>>> wrote:<br>><br>> A few months ago, I tried to convert our Version Control<br>> to SVN. In the middle of my eval tests, SVN was upgraded
<br>> resulting in my TortoiseSVN client being a newer than my<br>> command line tools. I used the command line tools to<br>> create my repositories but planned to provide the users
<br>> with TortoiseSVN. When I used the newer TortoiseSVN it<br>> changed the repository format so that the command line<br>> client could no longer access files. Same kind of errors
<br>> you are seeing. This feature caused so much trouble<br>> that I was forced to ClearCase, yuck.<br>><br>> Looks like you need to get the older client. One that<br>> matches your repository.
<br>><br>> ------------------------------------------------------------------------<br>> *From:* wplug-bounces+laweber=<a href="mailto:switch.com@wplug.org">switch.com@wplug.org</a>
<br>> <mailto:<a href="mailto:switch.com@wplug.org">switch.com@wplug.org</a>><br>> [mailto:<a href="mailto:wplug-bounces+laweber=switch.com@wplug.org">wplug-bounces+laweber=switch.com@wplug.org
</a><br>> <mailto:<a href="mailto:wplug-bounces+laweber=switch.com@wplug.org">wplug-bounces+laweber=switch.com@wplug.org</a>>]<br>> *On Behalf Of *Shane Liesegang<br>> *Sent:* Friday, February 16, 2007 2:04 PM
<br>> *To:* General user list<br>> *Subject:* [wplug] SVN upgrade -> mismatched RA version<br>><br>> I'm on a shared host that uses version 1.3.2 of<br>> Subversion, and I recently compiled and installed a
<br>> local copy of version 1.4.3.<br>><br>> Now when I try to run any svn commands, I get a<br>> message about mismatched RA versions.<br>><br>> $ svn help
<br>> svn: Mismatched RA version for 'dav': found 1.4.3,<br>> expected 1.3.2<br>> $ svn co http://{my_repo}<br>> svn: Mismatched RA version for 'http': found
1.4.3,<br>> expected 1.3.2<br>><br>><br>> Some googling showed that these errors happen when<br>> there's bits of old installs leftover from an upgrade.<br>
> Of course, in my case, the old version is still on the<br>> system. I get these even if I directly run the new<br>> binary (as opposed to trusting my $PATH).<br>>
<br>> Has anybody dealt with this before? Any words of<br>> advice on how to proceed? I'm afraid I hosed SVN. :-(<br>><br>><br>><br>><br>> ------------------------------------------------------------------------
<br>><br>> _______________________________________________<br>> wplug mailing list<br>> <a href="mailto:wplug@wplug.org">wplug@wplug.org</a><br>> <a href="http://www.wplug.org/mailman/listinfo/wplug">http://www.wplug.org/mailman/listinfo/wplug
</a><br>><br><br>_______________________________________________<br>wplug mailing list<br><a href="mailto:wplug@wplug.org">wplug@wplug.org</a><br><a href="http://www.wplug.org/mailman/listinfo/wplug">http://www.wplug.org/mailman/listinfo/wplug
</a><br></blockquote></div><br>