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

Re: problem migrating repository

From: <cmpilato_at_collab.net>
Date: 2002-08-01 21:08:48 CEST

Rich Drewes <drewes@interstice.com> writes:

> Hello,
> I am running an old version of Subversion (subversion-r1302.tar.gz) and I
> am trying to move my repository to a more recent version of SVN using the
> svnadmin dump technique described at
> http://svn.collab.net/repos/svn/trunk/notes/repos_upgrade_HOWTO . The
> version of svnadmin in r1302 does not even contain the dump option.
> I acquired the subversion-r2092f.tar.gz sources, and built the
> svnadmin-old binary with --disable-shared, but when I try to use this
> binary to svnadmin dump my repository I get this error:
> svn_error: #21086 : <Berkeley DB error>
> Berkeley DB error while creating `strings' table for filesystem /home/svn/repository-new/ncs/db:
> Invalid argument
> Does anyone have any suggestions for migrating my repository to a more
> recent version of SVN? Am I running a version of SVN too old to be
> compatible with any svnadmin dump capability? The web page above seems to
> imply that r2092 should be able to read any prior version's repository.

Your repository was created waaaaaaaaaay back in the day. You need to
first run the enable-dupkeys.sh script (necessary as of revision 1384)
on the original repos itself, *then* use the 2092 branch code to
`svnadmin dump' the repository, and THEN use the latest code to
`svnadmin load' it again.


I'm tired just thinking about it. You?

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 1 21:10:00 2002

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.