No, I didn't thought of it because it's a new server but then again its
bound to have some issues.
So you are saying this warning/error is due to faulty hardware?
I did re-do the migration again and this it didn't gave me the decompression
of svndiff data failed error. Although that error/warning below kept on
popping up.
Thanks, Ill check the hardware.
Network is also a good point to check. Esp. if someone checked in a file
between your two conversions.
But before I would suggest to
1.) run analyzeon your database
2.) grab the latest trunk of vss2svn and run again. I added a small
addition to the error message to output the failing file. Than we can
investigate this further.
Dirk
_______________________________________________
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
