Testing your dump file

During testing it may be handy to have the complete Spacely repository available on your own machine instead of just via the dump file. If you want to recreate the complete Spacely repository, you can do that like this:

svnadmin create /var/lib/svn/spacely
svnadmin load --quiet /var/lib/svn/spacely < spacely.dump

You can use these same commands for testing your new plockets dump file. Create a temporary subversion repository on your machine and load the sprockets product:

svnadmin create /var/lib/svn/temp
svnadmin load --quiet /var/lib/svn/temp < plockets.dump

This should just work. But you probably want to be certain that the resulting repository has exactly the same information as the original sprockets part of the spacely repository.

One simple way is to create svn exports of both repositories and compare them. If you have svn:externals in your repository, then it is best to ignore those. Create and compare two exports like this:

# Make an export from the Spacely repository:
svn export --ignore-externals --quiet http://spacely.space/svn/plockets plockets.ori
# Alternatively, make an export from your local Spacely repository:
svn export --ignore-externals --quiet file://var/lib/svn/spacely/plockets plockets.ori
# Make an export from your local temporary repository:
svn export --ignore-externals --quiet file://var/lib/svn/temp/plockets plockets.new
# See the differences between those two exports:
diff -r plockets.ori plockets.new

This should not give a lot of lines of output. You may see some output like this:

3c3
< # $Id: config.py 551 2006-09-19 13:04:49Z sashav $
---
> # $Id: config.py 507 2006-09-19 13:04:49Z sashav $

That is okay. That is just a part of a file that is automatically adjusted by subversion based on the version number in the repository. If you see other differences then that is an indication that something went wrong. You need to investigate then.