[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: substituting old svn by new; svn and bdb;

From: Ryan Schmidt <subversion-2007a_at_ryandesign.com>
Date: 2007-01-25 19:50:13 CET

On Jan 25, 2007, at 08:11, Goehring wrote:

> on my Scientific Linux system is svn 1.1.4 installed. After I
> installed
> the latest subclipse (subversion front end for eclipse) this
> changed my
> svn repository. I cannot access it anymore from svn 1.1.4:
>
> svn: This client is too old to work with working copy '/afs/uni-
> hohenheim.de/project/mas/Users/lgoehrin/Hohenheim/TestMipHandler';
> please get a newer Subversion client

No, your repository has not been changed at all. However, your
working copy has been updated to the new format introduced with
Subversion 1.4. (Apparently the version of Subclipse you got uses
Subversion 1.4.x libraries.) Now you must use only Subversion 1.4.x
or newer clients with that working copy.

> So I've build installed the latest svn and apr and bdb from source.
> Now I am having the following problems:
>
> 1)The "old" svn still exists. Typing svn does not call the new
> version.
> How can the old be uninstalled and be "overwritten" by the new one?

Where on disk is the old one installed? Where on disk did you install
the new one? You apparently installed the new one in a different
place than the old one existed. For example, perhaps the old one is
in /usr/bin/svn and the new one went into /usr/local/bin/svn.

How you remove the old version depends on how you originally
installed it. For example, is this a Unix-like system, such as Linux
or FreeBSD? If so, was Subversion originally installed with your
package manager? If so, use your package manager to uninstall it.

> 2)The new version cannot access the repository:
> svn: Commit failed (details follow):
> svn: Commit failed (details follow):
> svn: Unable to open an ra_local session to URL
> svn: Unable to open repository
> 'file:///afs/unihohenheim.de/project/mas/Users/lgoehrin/
> subversionRepository/trunk'
> svn: Unsupported fs type 'bdb'
>
> What do I have to do such that the Bdb libraries are moved to a
> standard directory such that svn and subclipse find them.

BDB was the standard repository type until Subversion 1.2.0, at which
point it was changed to FSFS. Since it looks like you created your
repository with Subversion 1.1.x or earlier, your repository is BDB-
based. But it looks like your new Subversion was compiled without BDB
support, either because use supplied the --without-berkeley-db switch
when configuring, or because the BerkeleyDB libraries could not be
found. Your options are to either make a version of BerkeleyDB
available to Subversion during the configure phase, or convert your
repository to FSFS. Personally, I recommend converting to FSFS. If
you want to do that, the FAQ tells you how:

http://subversion.tigris.org/faq.html#bdb-fsfs-convert

Note that since your new Subversion doesn't know how to access the
BDB-based repository, you would need to "svnadmin dump" using the old
version of Subversion, and then "svnadmin create" and "svnadmin load"
using the new version of Subversion.

-- 
To reply to the mailing list, please use your mailer's Reply To All  
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 25 19:50:49 2007

This is an archived mail posted to the Subversion Users mailing list.