Line termination error aborts import from SVN dump file
We're investigating import of source from PVCS to RTC. We're exporting
from PVCS using SVN dumpfile generated by the Polarian import tool. The error message provided "An error occurred uploading contents for revision 211 of file" was very terse, details include the name of the file where the problem occured. The RTC error log contains several stack traces, here is a fragment of one: !ENTRY com.ibm.team.scm.client.importz 4 0 2008-11-20 11:52:15.921 !MESSAGE An error occurred uploading contents for revision 211 of file '/.../content/readme.txt'. Upload will be retried with encoding ISO-8859-1 !STACK 0 com.ibm.team.repository.common.TeamRepositoryException: CRJAZ0040I I/O error preprocessing the stream: CRJAZ0216I The line delimiter (41) was LF (Unix) encountered but CRLF (Windows) was expected. at com.ibm.team.repository.client.internal.ContentManager$StreamLengthUtility.run(ContentManager.java:261) at com.ibm.team.repository.client.internal.ContentManager.storeContent(ContentManager.java:401) at com.ibm.team.scm.client.importz.internal.ChangeSetArchiveImporter.setContents(ChangeSetArchiveImporter.java:1080) at com.ibm.team.scm.client.importz.internal.ChangeSetArchiveImporter.setContents(ChangeSetArchiveImporter.java:988) <endStackTrace> RTC Server is 1.0 on AIX. RTC Client is 1.0.1 in Windows. PVCS export was done on the same Windows machine where the import is being attempted. This completely aborts the import after what seemed like a lot of files had been processed. Is it possible to work-around this problem? Note that we are bypassing import into SVN and then export from SVN assuming the SVN dump format is acceptable for import. Is it possible we need to import and export from SVN to get an acceptable import format? Thanks, Brian |
One answer
Brian,
From the error message, it appears that the SVN Dump file indicates that the file has Windows line feeds but, in reality, the file has UNIX line feeds. Unfortunately, it appears that the RTC content management facility fails when such a misconfiguration is encountered. The SVN dump importer was written with the assumption that the line delimiter associated with a file was correct. However, it appears that SVN (or PVCS) doesn't have this restriction. Unfortunately, the only way to fix the problem would be to fix the RTC importer. Please log a work item for this against the Source Control component. Michael P.S. You could try importing the data into SVN first as it is possible that the SVN import process would fix the inconsistency. Brian Gillan wrote: We're investigating import of source from PVCS to RTC. We're exporting |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.