Index of errors?

[aihtdikh]

I'll play too - another non-expert, I'm afraid.

You won't need to build the nightly yourself, that's what the nightly 
builds are all about ;)

Regarding the error messages...
I've been converting our repository project by project, slowly over the 
last year or so.
I did a bunch recently with the latest nightly (20071002) that went 
quite well - dare I say perfectly, even.
It would be nice to know what the errors mean, but these days I just 
treat them as warnings.
I always do a full directory comparison between a fresh checkout from 
VSS and a fresh working copy
from svn, and browse around in the history until I'm satisfied that 
everthing looks ok.
If that all checks out fine, then that's enough for me.
I suspect that the only places that hold explanations for the messages 
are the source,
and the brains of our apparently missing experts - who I hope are on 
holiday, lazing in the sun - they've earned it!
My thanks to those who dealt with VSS so that we don't have to!

Harun

> Ok, I'll play.  I hate to see that no one answered yet.  Certainly not
> the expert, but here goes.
>  
> I would recommend getting the most recent nightly build.  It will have
> many bugs fixed.  Unfortunately I think you have to build it yourself.
> There is an SVN archive and you have to down load active perl and some
> functions for it (I think).  I managed to do it without too many tries,
> so it couldn't be too hard.  I'm not a perl user but a muddled through.
>  
> Make absolutely sure you have run the analyze and repair on your VSS
> database.
>  
> None the less you are likely to wind up with some strange results.  Some
> of names and versions get real strange due to differences between unix
> and windows file and path naming conventions.  I wound up with quite a
> few invalid path names.  Honestly can't remember how I fixed all that.
> I may have edited some of the names in the intermediate file.  I seem to
> remember reading on this list that most of those bugs have been fixed,
> so maybe you won't have that problem.
>  
> Now that I've typed this, maybe the experts will post the real answers.
> Good luck though.
>  
> Scott
>  
>
>
> ________________________________
>
> 	From: vss2svn-users-bounces at lists.pumacode.org
> [mailto:vss2svn-users-bounces at lists.pumacode.org] On Behalf Of Bruce
> Wilson
> 	Sent: Wednesday, October 31, 2007 4:29 PM
> 	To: vss2svn-users at lists.pumacode.org
> 	Subject: Re: vss2svn-users Digest, Vol 19, Issue 7
> 	
> 	
> 	Wow, I didn't realize this question would bring such a hush on
> the list.  :-)
> 	
> 	Anybody there?
> 	
> 	
> 	
>
>
> Subject: 
> Index of errors?
> Date: 
> Mon, 22 Oct 2007 12:23:50 -0500
>
> 		I'm finally getting serious about migrating from VSS to
> SVN.  My new repository is up and live, now it's time for the messy
> work. 
> 		
> 		My first test (using 0.11 Alpha 1) produced an
> alarming-looking list of errors.  I know not to panic, but I'd like to
> see what I can do to improve on the situation before I do my final. 
> 		
> 		I looked around the Wiki for any index as to what each
> error means, how serious it is, and what (if anything) can be done to
> correct or compensate.  I came up empty.  This seems like a very useful
> thing to have, and if I could obtain some of this information, I'd be
> happy to turn this into one or more Wiki pages for future reference. 
> 		
> 		I'd also read that trunk may be more "stable" than 0.11
> Alpha 1.  Is there a good way to get a binary of trunk?  (Again, seems
> like this would be a good thing to update on the site.) 
> 		
> 		Thanks for all your (volunteer) help. 
> 		
>