Errors
In Import Mode, Perforce related p4-java messages are reported as warnings and should be verified, for example:
46.3 A:F - repo/trunk/my.file WARNING: p4java: //import/repo/trunk/my.file - file(s) up-to-date.
In Conversion Mode, errors are reported as Panics and an exception is thrown.
Problematic Subversion dump records can be extracted and sent to Perforce when it is not possible to send in the whole dumpfile. The extracted dumpfile only contains meta-data and the file content is removed and replaced with a block count.
During an exception note the Subversion revision and node ID (the example above has a revision number of 46 and a node number of 3). Then run the following command to extract the problematic record, for example:
$ java -jar dist/p4convert.jar --type=SVN --repo=mysvndump.dump --extract=46.3
searching for node: 46.3...
Node-path: repo/trunk/my.file
Node-kind: file
Node-action: add
Prop-content-length: 10
Text-content-length: 308
Text-content-md5: 6a339b6ccf2af72d77169ef29b98eb0b
Content-length: 318
PROPS-END
A file is then generated called node.46.3.dump and
will contain the Subversion record to be sent to Perforces, as well as the
Subversion meta-data (everything after searching for node:
46.3...).