Jon Hardcastle wrote:
2) Where were you 2months ago when i needed advise
like that!
Blissfully unaware of any of this, and thinking I'd never need to run
another vss2svn conversion in my life. :)
-Nathan
--- Nathan Kidd <[EMAIL PROTECTED]> wrote:
In the recent conversion I did I found it fairly
easy to :
1. svnamin load, observe on which revision it fails
2. 'svndumptool split' [1] the failing revision out
of the main dumpfile
such that you get A.dump (revisions before bad rev),
B.dump (the bad
revision) and C.dump (revisions after bad rev).
3. Open B.dump in your favourite editor that won't
mangle binary data
(vi!) and fix it. (Does a parent directory need to
be created? Is a
rename wrong? Forcibly "un-orphan" a file by
reconnecting its path to
its true parent, etc.) The format is pretty easy to
work with if you're
careful -- just copy an entry similar to what you
want and tweak.
4. svnadmin load A.dump, B.dump, C.dump
5. Goto 1, for any problem in C.dump.
I found this much faster than trying to change
something in the vss2svn
process, and it guaranteed working results.
-Nathan
[1] http://svn.borg.ch/svndumptool/
_______________________________________________
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
