Re: Replaying revisions in new repository

Thilo-Alexander Ginkel wrote:

> after migrating an existing VSS repository to subversion, I noticed
> that some files are missing from the migrated repository.

> Unfortunately, fixing the migration script and performing a new
> conversion is not an option as new revisions have already been
> committed to the subversion repository.

> Now, I am looking for a way to apply the commits which happened since
> the migration to a newly converted repository (which will contain the
> files previously missed during the migration).

> Will the following command sequence work although the revision numbers
> from the old repository will not match the revisions from the new one?

> svnadmin dump -r 4488:4517 --incremental /path/to/old/repository > diff.dump
> svnadmin load /path/to/new/repository < diff.dump

Following up to my own post...

After trying to apply the modifications to the new repository
(revision 4615) I get the following error:

SubversionException: ('Berkeley DB error while opening environment for
filesystem /var/lib/svn/SetupSpecialist/db:\nDB_RUNRECOVERY: Fatal
error, run database recovery', 160029)

'svn recover' reports "Recovery completed. The latest repos revision
is 4645.", but the error still persists.

So, what is the preferred way to apply a partial dump to a new
repository, which contains the same files (plus a few additional
files) as the repository from which the dump was generated, but
different revision numbers?

Regards,
Thilo

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 29 14:09:18 2004