24 Aug 2009 16:55
Re: Project site ? Orphaned files?
Toby Johnson <toby <at> etjohnson.us>
2009-08-24 14:55:06 GMT
2009-08-24 14:55:06 GMT
On Mon, Aug 24, 2009 at 5:55 AM, Cooke, Mark <mark.cooke <at> siemens.com> wrote:
PumaCode is still the "official" site; it will be migrated to Google Code hopefully shortly but that effort got stalled for a bit. I'll update Google Code with a note to that effect.
There's no such thing as "normal" in VSS :) Every archive is screwed up in its own unique way depending on usage patterns, length of use, moon phases etc. I would highly recommend that, before you run "analyze", you make a backup of the existing repo first. We've seen cases where running analyze makes it even more difficult to migrate rather than less.
In general my advice would be to convert the existing repo as-is, and then "fix" it using available Subversion tools (svndumpfilter etc.), rather than try to fix it first and then convert.
1) which is the official site ~ is it still pumacode.org (which seems to
have the latest update) or google code? Can you update the front page
of either with a note to point to the latest?
PumaCode is still the "official" site; it will be migrated to Google Code hopefully shortly but that effort got stalled for a bit. I'll update Google Code with a note to that effect.
2) I seem to get an awful lot of orphaned files. Using svndumpfilter to
cut out the orphaned files after one conversion drastically reduced the
size of the file. Is this normal? I know the VSS archives had never
had analyze run on them (but did not seem to have many errors when I did
run it against a copy)?
There's no such thing as "normal" in VSS :) Every archive is screwed up in its own unique way depending on usage patterns, length of use, moon phases etc. I would highly recommend that, before you run "analyze", you make a backup of the existing repo first. We've seen cases where running analyze makes it even more difficult to migrate rather than less.
In general my advice would be to convert the existing repo as-is, and then "fix" it using available Subversion tools (svndumpfilter etc.), rather than try to fix it first and then convert.
toby
_______________________________________________ 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
RSS Feed