for all others, that not took part in our private mail thread. My guess
for the reason for the problem are mixed copy-from revisions in a
labeling situation. That means, that we wanted to copy file labels
within one revision, where the copy-from revision was not the same.
Therefor I made a patch, that forces a revision break at each file label.
The outcome is indeed very interesting, because of two reasons:
1.) In each revision only one file is copyied to the labels directory.
Exactly as intendend. The item seems to be shared (3 times) and the
label is copiyed for each share. Also correct. But we still see mixed
revision here? This would mean, that one share is pinned to a different
version number. very strange... or my assumption is false.
Can you please post the content of the dumpfile at revision 2750 to
verify that each copy-from revision lists the same number?
2.) My patch should have generated more revisions. It is very
interesting to see, that both runs, the one from Werner and my patch
will both stop at 2750, even if both of them should have nothing in
common in the revision numbering.
I tried to force this problem with a small testdatabase, but could not
reproduce it here.
Regarding the "live" database, you can simply make a file copy of the
VSS files to your local computer and run the conversion from there. If
you do it in a silent minute, during the night, you could probaply get a
pristine copy.
Dirk
------- Committed revision 2750 >>>
<<< Started new transaction, based on original revision 2751
* adding path : labels/Ready for MS01 Validation
Run/MS00/Source/MicroSched
uler/os_core.c ...COPIED... done.
* adding path : labels/Ready for MS01 Validation Run/Verification
Suite ...
done.
* adding path : labels/Ready for MS01 Validation Run/Verification
Suite/Mic
roCOS-II ... done.
* adding path : labels/Ready for MS01 Validation Run/Verification
Suite/Mic
roCOS-II/Common ... done.
* adding path : labels/Ready for MS01 Validation Run/Verification
Suite/Mic
roCOS-II/Common/os_core.c ...COPIED... done.
* adding path : labels/Ready for MS01 Validation
Run/MS00/Source/MicroSched
uler/os_core.c ...COPIED... done.
* adding path : labels/Ready for MS01 Validation Run/Verification
Suite/Mic
roCOS-II/Common/os_core.c ...COPIED... done.
svnadmin: Invalid change ordering: new node revision ID without delete
_______________________________________________
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
