You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Alexey Larsky <al...@c-map.ru> on 2009/07/17 08:13:03 UTC
SVN to Perforce depot convertion problem
Hello, All!
I try convert svn depots to perforce with p4convert-svn tool. 4 of 5 depots
is converted OK.
Versions of software:
SVN version 1.4.2 (r22196) compiled Sep 1 2008,
06:37:46
P4 Rev. P4/LINUX26X86/2007.3/140107 (2007/11/20).
p4convert-svn p4convert-svn/LINUX26X86/2009.1.main/188871 2009 02 19
When I convert last svn depot, I get error "Fatal error; found illegal
file name! The sequence "..." is reserved by Perforce."
Conversions log is attached.
The path with wildcard "." or "*" in Perforce is illegal.
Can I able remove or rename this path in SVN depot somehow?
Database is FSFS type.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2371984
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: SVN to Perforce depot convertion problem
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Jul 17, 2009, at 08:18, Florian Weimer wrote:
>> 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.
Such careful editing should be possible using svndumptool.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2372156
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
RE: SVN to Perforce depot convertion problem
Posted by Tony Sweeney <ts...@omnifone.com>.
> -----Original Message-----
> From: Florian Weimer [mailto:fweimer@bfk.de]
> Sent: 17 July 2009 14:18
> To: Alexey Larsky
> Cc: users@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 <fw...@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@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@subversion.tigris.org].
Re: SVN to Perforce depot convertion problem
Posted by Florian Weimer <fw...@bfk.de>.
* 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.
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).
--
Florian Weimer <fw...@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@subversion.tigris.org].