Well, none of this completely surprises me. I've only been with the company for about 3 years. The particular archive, though, has dates within it dating back to around 1996. I really don't know the history of the archive beyond that, nor does anyone else who currently works in the company. I simply inherited the mess that is Visual SourceSafe. And that's the reason I'm trying to push a move to something else (specifically Subversion).
I do know, however (as you probably do as well), that Visual SourceSafe can easily be affected if the date / time of the client PCs is not correct at the time of a particular action. So, if they made changes to the DB and the client PC had an incorrect date, then you've effectively made a mess of your archive. For a DB that's nearly 10 years old, it's likely that at least once or twice the date was wrong on a system. So there's really no intentional "strange concepts" used in the archive maintenance. It's probably just an instance of me inheriting a messy DB. Sadly enough, this is a documented problem with VSS. I ran the VSS 2005 analyze utility against the DB and it found a large number of errors that the 6.0 analyze utility did not. However, when I try to do the load of the dump file into Subversion, it's failing at the same point. The only thing I can think of doing off the top of my head is for me to hack the conversion script to verify time linearity and if errors are found, to replace the out-of-sequence timestamp with a normalized stamp. This will give me some incorrect timestamps, but should be sufficient to get the data to load into Subversion. Any thoughts or comments about this approach? Thanks again for your assistance! jward. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Sent: Monday, June 05, 2006 8:21 PM To: Vss2Svn Users Subject: Re: pin_handler: another file history issue > ACBAAAAA shows the same problem, while YBBAAAAA seems to be ok. > > We need to push it a little further, can you look at BCBAAAAA, > CCBAAAAA, ...? > > Or can you send me your PhysicalAction.txt in a private mail? It seems that you have a lot of broken timestamps in your archive. It is not only a singular event. The broken timeline can be found on more unrelated items. The next problem is, that there isn't any regular pattern for this error. The timestamps vary up to one year, but without any logic behind it. What you could try is to remove the timecondition in the GetChildRecs function of vss2svn.pl. Probably this would help a little, but still sorting your actions by timestamp will give a complete unrelated mess. What strange concepts did you use, while maintaining your archive? 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
