On Thu, 3 Apr 2008 19:20:20, Richard Hughes <[EMAIL PROTECTED]> wrote: > I've finally got to the bottom of the last thing preventing me doing a > completely clean conversion. > > The same label was used three times, in three different > subdirectories. The problem is in the sanity checker, which doesn't > update its internal tree during the copy if the target directory > already exists (because of an earlier labelling of a child project). > When the third label happens the sanity checker thinks some parent > directories don't exist when they actually do so it adds them, > breaking the svnadmin load which knows that the directories really do > exist. If that description made no sense, read the test case at the > end of this e-mail. > > I've also attached a patch, as before. > > Richard.
Thanks a bunch for figuring that out. I haven't had to deal with a VSS to SVN conversion in a long while now, but last time I did I ran into this problem multiple times. I just wasn't brave enough to go through the sanity checker and try to figure out what was causing it, so I had to fix my dump files by hand. Great work! _______________________________________________ vss2svn-users mailing list Project homepage: http://www.pumacode.org/projects/vss2svn/ Subscribe/Unsubscribe/Admin: http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org Mailing list web interface (with searchable archives): http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.user
