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

RE: RE: RE: Perforce to Subverson Migration

From: Sumanjit Kaur Brar <SBrar_at_quark.com>
Date: Tue, 26 Aug 2008 12:41:56 +0530

Hi Mike,

Thanks for your reply n help. I think you are right. When I run the script it gives me follwong error :

p4_get_file_content: //depot/ProjectA/build/build.bat#10
'-' is not recognized as an internal or external command,
operable program or batch file.
Close failed: (256) at p42svn.pl line 752.

Do you have the script which you updated by any chance or any clue about the above error.

Regards,
Suman Brar

-----Original Message-----
From: Mike A [mailto:mabraham_at_monitor.com]
Sent: Monday, August 25, 2008 7:12 PM
To: users_at_subversion.tigris.org
Subject: RE: RE: Perforce to Subverson Migration

Hi:

You need to pipe the output of p42svn.pl to the SVN dump file, like this

perl p42svn.pl --branch //depot/projectA=trunk/projectA --debug --user abc
--password=123 > projectA.svndmp

Also, you had --branch incorrect - following the = should be an SVN path -
use p42svn --help to see an example.

I use version 0.21 of p42svn, but I don't remember which repo rev # I got.
I did have to fix a number of problems:

1) The logic for binary files uses some forking/piping (I don't recall the
details) which doesn't run under Windows;
2) The output dump file includes trailing slashes in paths which cause the
--parent-dir option of svnadmin load to assert;

HTH,

Mike

Sumanjit Kaur Brar wrote:
>
> Hi,
>
> Can anyone please help with the below query.
>
>
> Regards,
> Suman Brar
> -----Original Message-----
> From: Sumanjit Kaur Brar [mailto:SBrar_at_quark.com]
> Sent: Friday, August 22, 2008 3:09 PM
> To: vishwajeet singh
> Cc: users_at_subversion.tigris.org
> Subject: RE: Perforce to Subverson Migration
>
>
>
> I used the p42svn.pl(rev 75) available and the output which I get is :
>
>
>
> C:\Documents and Settings\harneetsingh\Desktop\test>perl p42svn.pl
> --branch //depot/projectA=d:\SVN\PERFORCE --debug --user abc
> --password=123
>
> Using an array as a reference is deprecated at
> C:/Perl/site/lib/Date/Format.pm line 216.
>
> Using an array as a reference is deprecated at
> C:/Perl/site/lib/Date/Format.pm line 322.
>
> process_options: branch //depot/projectA=> d:\SVN\PERFORCE
>
> process_options: branch //depot/projectA => d:\SVN\PERFORCE/
>
> SVN-fs-dump-format-version: 1
>
> p4_get_changes: branch //depot/projectA/
>
> Completed!
>
> I am not able to get the dump file which I can use in Subversion as
> dump/load format.
>
>
> Regards,
> Suman Brar
>
>
>
> -----Original Message-----
> From: vishwajeet singh [mailto:dextrous85_at_gmail.com]
> Sent: Friday, August 22, 2008 1:18 PM
> To: Sumanjit Kaur Brar
> Cc: users_at_subversion.tigris.org
> Subject: Re: Perforce to Subverson Migration
>
>
>
> http://p42svn.tigris.org/
> this might be of some help.
>
>
> On Fri, Aug 22, 2008 at 12:32 PM, Sumanjit Kaur Brar < SBrar_at_quark.com>
> wrote:
>
>
> Hi,
>
> I need to migrate code from Perforce(Windows Server) to Subversion(linux
> server). Any useful information/links/tips/help is greatly appreciated.
>
> Regards,
> Suman Brar
> Ext : 9878
>
>
>
>
> --
> Cheers,
> Vishwajeet
> http://www.singhvishwajeet.com
>
>
>
>

-- 
View this message in context: http://www.nabble.com/Perforce-to-Subverson-Migration-tp19102408p19144099.html
Sent from the Subversion Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-26 09:12:33 CEST

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.