If in fact that is the problem, how do I continue? Or can I? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Sent: Tuesday, October 24, 2006 1:33 PM To: Vss2Svn Users Subject: Re: ERROR -- FAILED with non-zero exit status 255
Kenneth Porter schrieb: > --On Friday, October 13, 2006 9:41 AM -0700 Mike Craig > <[EMAIL PROTECTED]> wrote: > >> TASK: IMPORTSVN >> >> ssphys: no file delta record found for check-in action (probably item >> did not re >> >> tained old versions of itself) >> >> Try `ssphys --help` for more information >> >> ERROR -- FAILED with non-zero exit status 255 >> >> at vss2svn.pl line 1092 > > During this phase, ssphys is used to extract each version of a file to > use in creation of the Subversion dump file. The error message is > saying that the extraction subcommand is failing to find the desired > version of a file in its physical file. > > Try to determine which physical file and version is failing, and run > the ssphys command "by hand". You can also run "ssphys info" on that > physical file and see if there are any anomalies in the XML structure > generated. (Not errors in the XML, but problems with the VSS structure.) Vss will allow you to set the flag "Store only latest version" at every time. So it might be possible, that the current state of the flag is to store revision deltas between each version, but at some point in time, this flag was not set. I assume, that this is a global setting and that we don't know the state of this flag in the history. We only know the latest state. During decoding, we will find delta records and we are able to generate older versions of the file, until we get to the point, where this flag was not set. Then we will see, that the file had a modification, but we don't know what was modified, so we are unable to extract any version prior to this point. ssphys will report this with an non zero exit status and the "wrong" message, that a "--help" could help you in resolving the issue. For vss2svn this will only mean, that we do not have versions of the file prior to this point. Another explanation for this could be a broken physical file, but this would probably result in a different message. 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 _______________________________________________ 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
