[p4] cvs2p4 - Newbie question

[Smith, Jeff]

I guess it depends on your business model.  Every company I've worked out decides they have to transition the history when changing CM systems.  Sometimes it's just too costly form a maintenance perspective to keep the old system up and running.  Usually there are several old versions of products in the field and to make a patch and move it forward would mean modifying code in both systems and having a way to migrate the changes from versions in the old system to versions in the new.  The upfront cost of conversion is usually far less (and more stable) than designing tools and processes to handle patches across CMS system. 

Jeff 

-----Original Message-----
From: perforce-user-bounces at perforce.com [mailto:perforce-user-bounces at perforce.com] On Behalf Of Niggemyer, K. Brant
Sent: Monday, December 18, 2006 3:39 PM
To: perforce-user at perforce.com
Subject: Re: [p4] cvs2p4 - Newbie question


 
Yep.  On every CVS -> Perforce conversion project I've worked on after weighing everything we ultimately decided to just import the tip from CVS, keeping this old CVS archive around for "reference".


-----Original Message-----
From: perforce-user-bounces at perforce.com [mailto:perforce-user-bounces at perforce.com] On Behalf Of David Alban
Sent: Monday, December 18, 2006 11:58 AM
To: perforce-user at perforce.com
Subject: Re: [p4] cvs2p4 - Newbie question

One of the nice perforce folks pointed out to me recently, if it's not necessary to transfer/convert/maintain the revision history *in perforce*, don't bother with cvs2p4.  Just add your files to perforce.

Besides, unless your cvs repository literally is going away (as opposed to just not being used for active development at some point), you can always go back and "consult" a static cvs repository for history.

[sent at 2006-12-18 08:57 PST]

--
David Alban <dalban at stubhub.com>
Release Engineering Tools
http://StubHub.com/

-----Original Message-----
From: perforce-user-bounces at perforce.com [mailto:perforce-user-bounces at perforce.com] On Behalf Of Ildefonzo Arocha
Sent: Monday, December 18, 2006 5:10 AM
To: perforce-user at perforce.com
Subject: [p4] cvs2p4 - Newbie question

Hello,

I am in the process of testing Perforce for our company.  I have downloaded the evaluation version for Linux 2.4 kernel.

One critical factor on the decision over Perforce is its possibility to convert our existing CVS repository, I am testing with cvs2p4 with no luck :(

When I try to run test/runtest I get the following error:

===== Lines referenced:
OneDB
Release_4_02_05
Release_4_03_01
Release_5_01_01
branch_Globopharm
cvs
shemp
warp
runtest> diff /iar/cvs2p4/cvs2p4-3.0b6/test/lines.good
runtest> /iar/cvs2p4/cvs2p4-
3.0b6/test_conv_dir/lines
2,8c2,7
< cabesa
< chupa
< curly
< curly2
< curly3
< ha
< larry
---
> OneDB
> Release_4_02_05
> Release_4_03_01
> Release_5_01_01
> branch_Globopharm
> cvs
10,12c9
< vtag
< xxx
< yyy
---
> warp
runtest: *** "diff /iar/cvs2p4/cvs2p4-3.0b6/test/lines.good
/iar/cvs2p4/cvs2p4-3.0b6/test_conv_dir/lines" exited with signal 0 status 1
runtest: *** genmetadata bad results
runtest> rm -f /iar/cvs2p4/cvs2p4-3.0b6/test/,v rm -f
runtest> /iar/cvs2p4/cvs2p4-3.0b6/test/xy,v
runtest> rm -f /iar/cvs2p4/cvs2p4-3.0b6/test/baÿÔdab,v

Whatever that means???!! I find no documentation about what this error is about, or how to get around it.

I ignored the error and tried a conversion, then I get the following error:

===== Lines referenced:
OneDB
Release_4_02_05
Release_4_03_01
Release_5_01_01
branch_Globopharm
cvs
shemp
warp
========== genchanges
Mon Dez 18 13:11:02 CET 2006
========== dochanges
Mon Dez 18 13:11:08 CET 2006
dochanges: cannot recognize p4d version in:

*** dochanges  FAILED

Not been a Perl programmer I was able to track down where the error is printed out to "p4d_vers" in "lib/util.pl"

sub p4d_vers
{
  my ($P4D) = @_;
  my $v = `$P4D -V`;
  my ($y, $r) = ($v =~ m/\nRev. P4D\/[^\/]+\/(\d+)\.(\d+).*\//);

  if (! $v || ! $r)
    { print "$Myname: cannot recognize p4d version in:\n$v\n"; exit 1; }

  return ($y, $r);
}

p4d and p4 are in my $PATH, I am working as root, and pfd -V outputs:

Perforce - The Fast Software Configuration Management System. Copyright 1995-2006 Perforce Software.  All rights reserved. Portions copyright 1991-2005 Compuware Corporation. Rev. P4D/LINUX24X86/2006.1/109255 (2006/10/17).
License: none

So something is not getting correctly parsed, don't know where, and don't know if I should even modify this file.

Can anyone help me here?  I have one week for testing a whole bunch of stuff and convincing the management why Perforce is a must.

I am no Linux expert and have no experience with Perforce, so please be gentle with the answers!

Red Hat Linux, Kernel 2.4
Perforce 2006.1

Thanks in advance,
Ildefonzo
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com http://maillist.perforce.com/mailman/listinfo/perforce-user

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com http://maillist.perforce.com/mailman/listinfo/perforce-user

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com http://maillist.perforce.com/mailman/listinfo/perforce-user