[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: CONFLICTS in cvs2svn.py output

From: Scott Lamb <slamb_at_slamb.org>
Date: 2002-12-12 08:00:42 CET

Tim Moloney wrote:
> No matter what CVS repository I try to convert, I see
> CONFLICTS: '_fc601008_p_char'
> for every commit.
> Should I be worried about this? Is it a cosmetic bug? I've had
> a lot of problems getting swig working that I don't want to assume
> anything.

FWIW, I also get this message on the latest cvs2svn-mmacek, and I had
little trouble installing the swig bindings. This is now the _only_
problem I have with cvs2svn. It's a little disconcerting, but
cvs2svn-mmacek appears to have successfully converted my entire
repository, branches and all, totally correctly. mmacek and his cvs2svn
regression tests have worked wonders, I guess...

Now I can finally compare repository sizes, too. My repository (with an
unhealthy number of binary files; many Oracle Forms/Reports and one
horrible, grotesquely oversized Microsoft Access file) is 100MB with
CVS, 296MB right after cvs2svn, and only 66MB after pruning obselete logs.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Dec 12 08:01:01 2002

This is an archived mail posted to the Subversion Dev mailing list.