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

RE: SVN to Perforce depot convertion problem

From: Tony Sweeney <tsweeney_at_omnifone.com>
Date: Fri, 17 Jul 2009 15:45:02 +0100

> -----Original Message-----
> From: Florian Weimer [mailto:fweimer_at_bfk.de]
> Sent: 17 July 2009 14:18
> To: Alexey Larsky
> Cc: users_at_subversion.tigris.org
> Subject: Re: SVN to Perforce depot convertion problem
>
> * Alexey Larsky:
>
> > Can I able remove or rename this path in SVN depot somehow?
>
> You could use "svnadmin dump" to create a dump, carefully
> edit its output, load it into a new repository, and convert that.

That's one way, and the only way to fix this on the Subversion side. However, p4convert-svn claims to be able to do incremental imports. See: ftp://ftp.perforce.com/private/outgoing/p4convert-svn-README.txt

The relevent section reads:

PERFORMING AN INCREMENTAL IMPORT
--------------------------------

  Incremental conversion is when you take a contiguous block of changes
  from Svn to Perforce. The block must not include changes that you
  have already converted. If you skip any changes in Svn, you can't
  go back and get them if you've converted any later changes.

  For instance, you might initially go from 1 -> HEAD, then after some
  continuing use of the Svn repository, convert from the old HEAD
  was to the new HEAD. Here's an example with actual numbers:

     run 1: 1 -> 100
         2: 101 -> 145
         3: 146 -> 209

  The corresponding commands might look like this:

     p4convert-svn file:///conv/svn_root svn ../helper.xml 1 100
     p4convert-svn file:///conv/svn_root svn ../helper.xml 101 145
     p4convert-svn file:///conv/svn_root svn ../helper.xml 146 209

  When starting the conversion again, you'll see "Searching, skipping rev X"
  for each Svn revision that you already converted. This is normal.

So, you may be able to skip the commit with the bad path (from Perforce's point of view).
(and which seems to have been committed in error in the first place, from the log).

>
> If you want to fix things on the Perforce side, you need to
> ask on a Perforce mailing list (if there is such a thing).

perforce-user (at) perforce.com

And, of course, support (at) perforce.com if you are actually paying.

>
> --
> Florian Weimer <fweimer_at_bfk.de>
> BFK edv-consulting GmbH http://www.bfk.de/
> Kriegsstraße 100 tel: +49-721-96201-1
> D-76133 Karlsruhe fax: +49-721-96201-99
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&
> dsMessageId=2372058
>
> To unsubscribe from this discussion, e-mail:
> [users-unsubscribe_at_subversion.tigris.org].
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit
> http://www.messagelabs.com/email
> ______________________________________________________________________
>

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2372082

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