You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Christophe Labouisse <ga...@tigris.org> on 2003/11/13 21:03:42 UTC

SymDiffParent in cvs2svn 0.51

When trying to import my whole CVS repository with cvs2svn.pl 0.51 I run
into the following error:

--! Pass 4: failed 'Could not find single parent for 'start', canditates
was:'ObjMHlpr','v6_0','CLLib','v1_3','athal','DBDDb-1','zcrdlpo','Utils'
Please, read about this event to avoid this error: SymDiffParent' in 1
(for 27 total) seconds.

As far as I understand the problem is that I gave the same stupid
"start" vendor tag to a bunch of projects when importing them into CVS.

As far as I understand cvs2svn tells me to look at the SymDiffParent
event. First problem, there is no SymDiffParent event but a
DiffSymParent. Is is a spelling problem (beside there is a trivial
spelling problem: "canditates" instead of "candidates" in the error
message). Second problem, if I rerun cvs2svn.pl with "-i DiffSymParent"
I still run into the same error.



-- 
Le cinéma en Lumière : http://www.lumiere.org/

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org


Re: Re[2]: SymDiffParent in cvs2svn 0.51

Posted by "C. Michael Pilato" <cm...@collab.net>.
Lev Serebryakov <le...@serebryakov.spb.ru> writes:

>   I named my *project* (not only script, but whole project)
>   cvs2svn.pl, distribution archive named `cvs2svn.pl' (not simple
>   `cvs2svn'), you could not see it, but  directory on my SVN
>   repository named `cvs2svn.pl'. Full name of my project is cvs2svn.pl.

Oh, I totally get that.  I'm just saying that often people refer to a
script without it's .pl or .py or .sh or ...  "cvs2cl", for example, is
many times found as cvs2cl.pl.  "cvs2svn" is found as cvs2svn.py.  To
be honest, when I say cvs2svn.pl the first time, I thought, "Hm,
somebody has actually gone through the trouble of porting cvs2svn.py
to Perl."  Obviously, this isn't what you've done, but...

Can you the see the opportunity for confusion here, and how it could
have really easily been avoided?

Sorry.  I should be talking about this on your new list.  :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re[2]: SymDiffParent in cvs2svn 0.51

Posted by Lev Serebryakov <le...@serebryakov.spb.ru>.
Hello, B.!
Friday, November 14, 2003, 12:33:16 AM, you wrote:

 Ok, I'll not discuss cvs2sbn.pl after this message here, you are
 right, I need different mailing list for it, and I'll do it.

>> I have two strong opinions regarding cvs2svn.pl:
>>    1.  It is carelessly named, as it will inevitably be confused with
>>        cvs2svn.py.  My recommendation is that the author be a little
>>        more creative, and a lot more sensitive to the fact that
>>        scripts are often referred to without their
>>        interpreter-indicating filename extensions.  In my mind,
>>        "cvs2svn" *means* cvs2svn.py -- don't mess with my head.
  I named my *project* (not only script, but whole project)
  cvs2svn.pl, distribution archive named `cvs2svn.pl' (not simple
  `cvs2svn'), you could not see it, but  directory on my SVN
  repository named `cvs2svn.pl'. Full name of my project is cvs2svn.pl.

>>
>>    2.  It is not part of Subversion itself, does not live in
>>        Subversion's tree, and is not distributed with Subversion.  So
>>        please, while it's fine to announce new releases here, kindly
>>        take further discussion to a list dedicated to this entirely
>>        different product.
  Good point. I agree. I'll prepare list form my script today.

BWF> I've got another one right here:

BWF> 3. cvs2svn.py is the result of hundreds of man-hours and a helluva lot
BWF>    of careful testing of a helluva lot of tricky edge cases, gargantuan
BWF>    repositories, and busted RCS files.  Why should I trust my
BWF>    *historical*data* to a script that has no visible test suite?
   Visible test suit is FreeBSD repository at point of version 4.7. Is
  it enough? Some parts  of it could not be converted with my script
  due to FATAL errors (like revisions 1.1.2.1, which is format
  violations, etc). But parts, which could be PARSED converted well
  with some help from user, and FAILED without this help.

   Also, I've tested my script on test suite from cvs2svn.py. Only three
  errors was found. And they are fixed now (and fixes will be in next
  release).

   Also, my script is over-paranoid by default *especially* to avoid
  historical data loss. It is like a cat: ``when you are not sure,
  wash yourself''. My script, when it is not sure, asks user.  It will
  complain about DOZENS situations, when it will works properly with
  simple ignoring occurred ``error''. I think, that better here will
  be second try with options from user, than some ambiguous decision
  will be done, because `any of these elements could be selected, this
  element is first in array, lets select it'.

   And cvs2svn.py with "big visible test suite" munch many parts of
  FreeBSD repository (and repositories of my project!) without any
  error, and after that dump are broken or created from this dump
  repository contains bad branches, etc.

    Also, I don't see how I could help cvs2svn.py -- I could not give
  any hints to it, but --only-trunk, which is not a solution in most
  cases :(

               Lev Serebryakov


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: SymDiffParent in cvs2svn 0.51

Posted by "Sergey A. Lipnevich" <se...@optimaltec.com>.
Not that this is any of my business, I actually agree with #2, but #3
sounds too protectionist. You're assuming too much. Lev might actually
be doing a good job promoting Subversion in his own way, and the
principal difference with cvs2svn[.py] that I see is that the .pl
provides more controls for users. They may choose to use it.
I can understand your disappointment though because of the confusion
created by this script.

Sergey.

B. W. Fitzpatrick wrote:
> 
> 3. cvs2svn.py is the result of hundreds of man-hours and a helluva lot
>    of careful testing of a helluva lot of tricky edge cases, gargantuan
>    repositories, and busted RCS files.  Why should I trust my
>    *historical*data* to a script that has no visible test suite?
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: SymDiffParent in cvs2svn 0.51

Posted by "B. W. Fitzpatrick" <fi...@red-bean.com>.
"C. Michael Pilato" <cm...@collab.net> writes:
> Christophe Labouisse <ga...@tigris.org> writes:
> 
> > When trying to import my whole CVS repository with cvs2svn.pl
> > 0.51...
> 
> Christophe, this is not aimed at you.  I'm just using your mail as a
> springboard.
> 
> I have two strong opinions regarding cvs2svn.pl:
> 
>    1.  It is carelessly named, as it will inevitably be confused with
>        cvs2svn.py.  My recommendation is that the author be a little
>        more creative, and a lot more sensitive to the fact that
>        scripts are often referred to without their
>        interpreter-indicating filename extensions.  In my mind,
>        "cvs2svn" *means* cvs2svn.py -- don't mess with my head.
> 
>    2.  It is not part of Subversion itself, does not live in
>        Subversion's tree, and is not distributed with Subversion.  So
>        please, while it's fine to announce new releases here, kindly
>        take further discussion to a list dedicated to this entirely
>        different product.

I've got another one right here:

3. cvs2svn.py is the result of hundreds of man-hours and a helluva lot
   of careful testing of a helluva lot of tricky edge cases, gargantuan
   repositories, and busted RCS files.  Why should I trust my
   *historical*data* to a script that has no visible test suite?

-Fitz

--
Brian W. Fitzpatrick    <fi...@red-bean.com>   http://www.red-bean.com/fitz/


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: SymDiffParent in cvs2svn 0.51

Posted by "C. Michael Pilato" <cm...@collab.net>.
Christophe Labouisse <ga...@tigris.org> writes:

> When trying to import my whole CVS repository with cvs2svn.pl
> 0.51...

Christophe, this is not aimed at you.  I'm just using your mail as a
springboard.

I have two strong opinions regarding cvs2svn.pl:

   1.  It is carelessly named, as it will inevitably be confused with
       cvs2svn.py.  My recommendation is that the author be a little
       more creative, and a lot more sensitive to the fact that
       scripts are often referred to without their
       interpreter-indicating filename extensions.  In my mind,
       "cvs2svn" *means* cvs2svn.py -- don't mess with my head.

   2.  It is not part of Subversion itself, does not live in
       Subversion's tree, and is not distributed with Subversion.  So
       please, while it's fine to announce new releases here, kindly
       take further discussion to a list dedicated to this entirely
       different product.
     

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org