Due to a miscomputation at startup on the second visit for the SvnLoaderFromRemoteDump,
this had a range of svn commit [1-0]. That in turn made the svn loader resolve an
unknown revision number. This should have been an uneventful visit from the start.
This commit fixes it.
Related to T3622