Richard Hughes 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.
Thanks Richard, I still don't have my VSS environment recreated but your
patches and descriptions make sense so I've committed them in r338. Glad
you were able to get a clean migration eventually!
toby
_______________________________________________
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
