[p4] perforce-user Digest steps to migrate to the perforce, Vol 47, Issue 22

praveen m sharp859 at gmail.com
Wed Nov 26 12:53:01 PST 2008


Hi I need a help to migrate CVS to Perforce,Please could any body mention
precautions i shoudl take and step by step process from scratch.

Thanks,
praveen

On Wed, Nov 26, 2008 at 12:00 PM, <perforce-user-request at perforce.com>wrote:

> Send perforce-user mailing list submissions to
>        perforce-user at perforce.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://maillist.perforce.com/mailman/listinfo/perforce-user
> or, via email, send a message with subject or body 'help' to
>        perforce-user-request at perforce.com
>
> You can reach the person managing the list at
>        perforce-user-owner at perforce.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of perforce-user digest..."
>
>
> Today's Topics:
>
>   1. Re: Guidelines for codelines? (Robert Cowham)
>   2. very basic problem starting p4d (Mark Tigges)
>   3. Re: very basic problem starting p4d (Dave Lewis)
>   4. CM Synergy to Perforce Migration (Kamlesh Mutha)
>   5. Re: CM Synergy to Perforce Migration (Evgeny)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 25 Nov 2008 23:35:59 -0000
> From: "Robert Cowham" <robert at vizim.com>
> Subject: Re: [p4] Guidelines for codelines?
> To: <perforce-user at perforce.com>
> Message-ID: <20081125233602.272A2C1E7D at davie.textdrive.com>
> Content-Type: text/plain;       charset="us-ascii"
>
> An excellent discussion and some really useful points.
>
> I agree with Rick M that to my mind resolving conflicts in my workspace
> before submitting when working on a shared mainline is conceptually just
> the
> same as merging changes into a branch (before copying back to main). And as
> he says I find it more risky because the only copy of my changes before I
> attempt to resolve against head is the workspace copy, and I might make a
> mistake and mess up the resolve while overwriting my changes. Merging into
> a
> branch and getting it wrong can be fixed by reverting and reintegrating
> (usually|).
>
> An interesting case I came across was a company doing agile development and
> working against a single mainline. They were doing TDD and made sure that
> builds/tests were fine before checking in. So the code in their workspace
> was the previous stable mainline, let us say at configuration X, plus their
> immediate change and its supporting tests, which we can call A, usually up
> to a small number of hours of work in a pair. X is valid, so is X + A
> (because it builds and tests work). So they check it in. Most of the time
> life was good.
>
> Sometimes they had to resolve a conflict. As previously they start with X,
> made changes A, and meanwhile someone else checked in changes B. A and B
> are
> not 100% compatible and require a merge which results in the latest state
> being X + B + A'. Usually this was not a problem, but from time to time the
> business would not authorise the release of A and yet wanted everything
> else
> to be released. Using their mainline only model (with release branches),
> they could not go back and find A because what had been checked in was A'.
> A
> itself had existed in the workspace but been slightly modified during the
> resolve with B. If they had been using Perforce, what I would have
> suggested
> is a tool to do the equivalent of a "shelve" (sparse branch) of A before
> resolving conflicts, such that at least A was safely tucked away and
> indentifiable unambiguously in the future should it ever prove necessary to
> identify it.
>
> OK, the above is perhaps a touch esoteric, but interesting nevertheless -
> caused them pain from time to time.
>
> Many other good points in the thread made which I agree with:
>
> - no single best solution for all situations - instead some good patterns
> which have their individual indicators and contra-indicators
>
> - branching strategy is a part of software engineering and shouldn't
> attempt
> to solve the problem in isolation
>
> I think it has been educational for all!
>
> Robert
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 25 Nov 2008 21:24:19 -0800
> From: "Mark Tigges" <mtigges at gmail.com>
> Subject: [p4] very basic problem starting p4d
> To: perforce-user at perforce.com
> Message-ID:
>        <e5679a210811252124tf0ef22bl683262719de17a81 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> I'm trying to set up p4 for personal home use.  I downloaded the cl
> client and p4d, and have had very little luck.  Here's what I'm trying
> to do:
>
> bash-3.1$ /synology/sw/p4/bin/p4d -d -r /synology/sw/p4/root -J
> /var/log/p4-journal
> Perforce server error:
>        Database open error on db.counters!
>        BTree is corrupt!
>        lock: : No locks available
>
> I've gone through the docs about how to set up a new root / depot, but
> have found nothing.  Following the directions at
>
>
> http://www.perforce.com/perforce/doc.081/manuals/p4sag/01_install.html#1063149
>
> yielded the above error.
>
> I'm kind of at a loss, but I also think there must be something
> simple. And yes /synology/sw/p4/root is rwx for the user.
>
> Thanks for any help,
>
> Mark.
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 26 Nov 2008 01:10:46 -0600
> From: "Dave Lewis" <dlewis78731 at gmail.com>
> Subject: Re: [p4] very basic problem starting p4d
> To: "Mark Tigges" <mtigges at gmail.com>
> Cc: perforce-user at perforce.com
> Message-ID:
>        <4870e8e10811252310x3fbf54aeh2874da327063a24c at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> do any of the db.* files exist in the root?
>
> On Tue, Nov 25, 2008 at 11:24 PM, Mark Tigges <mtigges at gmail.com> wrote:
>
> > I'm trying to set up p4 for personal home use.  I downloaded the cl
> > client and p4d, and have had very little luck.  Here's what I'm trying
> > to do:
> >
> > bash-3.1$ /synology/sw/p4/bin/p4d -d -r /synology/sw/p4/root -J
> > /var/log/p4-journal
> > Perforce server error:
> >        Database open error on db.counters!
> >        BTree is corrupt!
> >        lock: : No locks available
> >
> > I've gone through the docs about how to set up a new root / depot, but
> > have found nothing.  Following the directions at
> >
> >
> >
> http://www.perforce.com/perforce/doc.081/manuals/p4sag/01_install.html#1063149
> >
> > yielded the above error.
> >
> > I'm kind of at a loss, but I also think there must be something
> > simple. And yes /synology/sw/p4/root is rwx for the user.
> >
> > Thanks for any help,
> >
> > Mark.
> > _______________________________________________
> > perforce-user mailing list  -  perforce-user at perforce.com
> > http://maillist.perforce.com/mailman/listinfo/perforce-user
> >
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 26 Nov 2008 19:05:24 +0530
> From: "Kamlesh Mutha" <mkamlesh at gmail.com>
> Subject: [p4] CM Synergy to Perforce Migration
> To: perforce-user at perforce.com
> Message-ID:
>        <31fd96c90811260535o2cb849c2k56861fb369b8a0a0 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi All,
> We are using CM Synergy 6.5 as our SCM tool and are planning to migrate to
> Perforce in near future.
>
> I was just wondering if anybody has already worked on this migration and
> has
> some experience/"how to" to share?
>
> Thanks,
> Kamlesh.
>
> --
> Faith waiting in the heart of a seed promises a miracle of life which it
> can
> not prove!
> -Ravindranath Tagore
>
>
> ------------------------------
>
> Message: 5
> Date: Wed, 26 Nov 2008 16:39:58 +0200
> From: Evgeny <evgeny.zislis at gmail.com>
> Subject: Re: [p4] CM Synergy to Perforce Migration
> To: "Kamlesh Mutha" <mkamlesh at gmail.com>
> Cc: perforce-user at perforce.com
> Message-ID:
>        <b6840c770811260639x47feddcaw829015f06ce05fbb at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> I second that. We also have several project in Synergy that would like to
> move to Perforce at some point, but it seems that there is no information
> about how to go about something like that.
> All and any information appreciated.
>
> Regards,
> Evgeny
>
> On Wed, Nov 26, 2008 at 15:35, Kamlesh Mutha <mkamlesh at gmail.com> wrote:
>
> > Hi All,
> > We are using CM Synergy 6.5 as our SCM tool and are planning to migrate
> to
> > Perforce in near future.
> >
> > I was just wondering if anybody has already worked on this migration and
> > has
> > some experience/"how to" to share?
> >
> > Thanks,
> > Kamlesh.
> >
> > --
> > Faith waiting in the heart of a seed promises a miracle of life which it
> > can
> > not prove!
> > -Ravindranath Tagore
> > _______________________________________________
> > 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
>
>
> End of perforce-user Digest, Vol 47, Issue 22
> *********************************************
>



-- 
With Best Regards,
Pravin



More information about the perforce-user mailing list