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

Re: Suggestions for CVS conversion script

From: Richard Meade <richard.meade_at_shenick.com>
Date: 2005-03-11 12:47:37 CET

On Fri, 11 Mar 2005 10:17:13 -0000, Richard Meade
<richard.meade@shenick.com> wrote:

> Could you tell me how you resolved the problem in your case?

In case this is sparks any thoughts in anyone about the cause
- I added some trace to cvs2svn, in the while(1) loop of
filling_guide_for_symbol:
       line = self.symbolings.readline().rstrip()
       if not line:
         break
       print 'RJM: line=%s' % line
       name, revnum, type, svn_path = line.split(" ", 3)

Setup:
1) Import 7K files into CVS (Rev #2)
2) Modify 3 files & commit (Rev #3)
3) tag as 'Tag_1' (Rev #4)
4) Repeat 2&3: Tag_2(Rev 5&6),Tag_3(Rev 7&8),Tag_4(Rev 9&10)

 From what I can see on stdout during the cvs2svn run:

1) The same file is processed twice in the one tag:
   RJM: line=Tag_1 00000003 O trunk/shenick/Makefile
   RJM: line=Tag_1 00000003 O trunk/shenick/diversifEye/Makefile
   RJM: line=Tag_1 00000003 O trunk/shenick/framework/Makefile
   RJM: line=Tag_1 00000005 C trunk/shenick/Makefile

2) Revision 5 should be part of Tag_2, but seems to be in Tag_1
(based on the last line in 1) above)

3) On each tag after the first, it tries to check files
back into trunk instead of tags (or even branches):
   Starting Subversion commit 6 / 10
   RJM: <__main__.SymbolicNameFillingGuide instance at 0x01490D00>-->Tag_2
   RJM: svn_revnum=6
   RJM: line=000002 O trunk/shenick/build_no

Any suggestions would be most gratefully received... :-)
Thanks,
Richard.

-- 
Richard Meade
Shenick Network Systems
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 11 12:41:20 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.