This is reproducible using r8542 of cvs2svn.py, when run on the GtkRadiant repository associated with issue #1427 like so: $ cvs2svn.py --create -s svnrepos GtkRadiant/libs Because r8542 does not have the bugfix of r8544, the dumpfiles produced will attempt to copy paths from non-existent revisions -- specifically, from the revision currently in progress. Here's what it looks like when you do it with --dump-only followed by manual 'svnadmin create; svnadmin load': ------- Committed revision 439 >>> <<< Started new transaction, based on original revision 440 * adding path : trunk/picomodel.h ... done. * adding path : trunk/igl_to_qgl.h ... done. * adding path : branches/merge-1_2_10-post ...subversion/libsvn_fs/err.c:108: (apr_err=160006) svn: Reference to non-existent revision '440' \ in filesystem 'svnrepos/db' Errors like this ought to make cvs2svn stop in its tracks, but it just continues with the next revision. Oops! Some simple exit status checking should fix this.