I'm still getting a large number of errors/warnings about database
issues even though my vss analyze is now pretty clean (there is still
one issue about a corrupt file which might prevent old versions from
being recovered): Here are some of the most often repeated messages.
Perhaps this dooms my efforts.
ssphys: unknwon record type "œ7" detected (offset 0x8f7) TASK:
This really sounds like a broken phyiscal file. Can you run with --debug
and --verbose to see which file is the borken one? Then try to move the
phyiscal file out of your data folder and rerun again. But I expect,
that this is not the root of the problems.
BUILDACTIONHIST ERROR -- Attempt to add entry 'YBAAAAAA' with unknown version
number (probably destroyed) at vss2svn.pl line 745 ...
This is not a "error" message, more informational. I need to change this.
ERROR -- Attempt to commit unknown item 'UBSAAAAA': at vss2svn.pl line 745
This sounds like a broken timeline. One commit record has a time stamp
earlier than the add/create time. So we will see a commit before we have
added the file to the database. The current vss2svn converter does not
perform a check the linearity of the timestamps. This would be difficult
anyway, but at least we could check for linearity and report any
possible errors. Can you try to run "ssphys info UBSAAAAA" and check
your timestamps on each version?
ERROR -- Attempt to share unknown item 'KROBAAAA': at vss2svn.pl line 745
I expect the same here. We have some item related activities before we
have added the file.
By the way, this can happen very easily if you had a one computer in the
network with a wrong time. Every client will enter it's own timestamp to
the version records. There is no idea about a global time.
ERROR -- Parent path missing while trying to add item '/orphaned/_IDAAAAAA/abom/' at revision 94: adding missing parents at vss2svn.pl line 891
This is ok. We have found a orphaned item and we are going to add it to
a specific directory. This directory must be created before.
However, in addition to the above, I do see a number of perl warnings:
Use of uninitialized value in concatenation (.) or string at
/PerlApp/Vss2Svn/ActionHandler.pm line 264.
Use of uninitialized value in join or string at vss2svn.pl line 789.
Use of uninitialized value in concatenation (.) or string at
/PerlApp/Vss2Svn/ActionHandler.pm line 640.
Ok, this is more complicated, but I expect also, that this is due to the
timestamps problem.
As a next step I would suggest to add a new basic time stamp check. This
check could simply check for the linearity of the activities on each
physical file. If one time stamp is out of order, we could move it to
the timestamp between the two actions. Again, this is problematic, but
would help to get the archive converted. It will however mess up your
labels.
Can you do Perl programming? The best place to do this is in the
GetVssItemVersions function. I will give it a quick try...
Best regards
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
