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

RE: pvcs to svn migration

From: Bob Archer <bob.archer_at_amsi.com>
Date: Thu, 17 Sep 2009 10:18:32 -0400

> I am using svn importer tool to migrate PVCS repos to svn, but end up with errors. Could you help me to sort this? Please find the attachment of the config properties file, and error logs

It's been quite a while since I did this and you deleted all the directions for the pvcs config items so I can't recall what you are supposed to put in each one.

I think what is happening is that your export isn't doing anything... and it is trying to do the import and no dump was created. I expect this is because you project path and subproject are wrong.

The first think I would recommend is to take the import out of the equation. You can do that manually after you get the dump file. So change this to:

Next, verify that pvcs.project path is correct. You have it set to c://sky . Is that the path to your pvcs repository? The pvcs repository is the one that contains the "archives" folder.

Then you have pvcs.subproject set to .

I think you should leave this blank if you want to import the full pvcs repository into it.

If you look at the log your configuration is causing it to create this comnand line:

pcli.exe run ->C:/PVCS/temp/local/pvcs.tempdir/files.tmp -q listversionedfiles -prC://sky -l -z /.

I am guessing if you run that command you will not get any output. This is the file that drives the exporter... it reads this file that lists all the versionsed files and start getting them and building the dump file. So, until you can formulate a command with the correct project path and subproject paths and get this to create a file with a list of versioned files nothing is going to happen.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-17 16:19:29 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.