Jeff,
I'm not sure if there's an easier way to do this, but I would use the
svn 1.0 binaries if you still had them, to dump the old repo (only the
revisions since the ones you've loaded into the new repo). You can then
load this incremental dump into the new repo.
You might also want to use FSFS as the backend for 1.4 as it is now the
preferred backend, and you will likely run into similar trouble in the
future should you stay with Berkley db.
Russ
Jeff S wrote:
> Moved from svn 1.0.x to 1.4. The dump file was loaded
>
> unto new svn. Other developers had commits that were
> not included in the dump file that was loaded for the
> new svn.
>
> They are now getting error that revisions are not in
> sync, and svn won't let me update.
>
> Tried to do another dump of orignal repo but the new
> install of svn complains that the version of BerkelyDB
> no longer matches - so I cannot get dump file.
>
> They are trying to commit at revison 2651 but the
> loaded svn repo is back at revision 2644. How can I
> force the svn repo or client working copy revision
> levels to match up for a commit? Or is there
> another way to handle this?
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 6 21:26:05 2006