It's all about the answers!

Ask a question

Problems occured running import from CVS


Jeff Taylor (7673) | asked Apr 23 '09, 2:41 p.m.
I am having issues trying to import source from CVS into the Jazz SCM. I consistently get the same result. Here is the information in the error dialog I get:

"Importing from CVS"
Problems occured running importing from CVS.
Reason: A client error occured while trygin to create change set archive /home/jmtaylor/archive.tar

This error message does provide enough information as to the possible cause of the problem. If there some other debug information or log that I can check?

Here are the steps I have been following:
- Open the CVS Repositories view in my RTC 2.0 Beta client
- Navigate to my top level folder called "catt", under HEAD
- Right click and select Import into Jazz
- Select import as top-level folders
- Import into a change set archive file
- Keep the change set archive
- filename: /home/jmtaylor/archive.tar
- press Finish

Could it be a compatibility issue with the CVS server? What information would I need to check?

9 answers



permanent link
Jakub Jurkiewicz (59632) | answered Apr 24 '09, 5:29 a.m.
I am having issues trying to import source from CVS into the Jazz SCM. I consistently get the same result. Here is the information in the error dialog I get:

"Importing from CVS"
Problems occured running importing from CVS.
Reason: A client error occured while trygin to create change set archive /home/jmtaylor/archive.tar

This error message does provide enough information as to the possible cause of the problem. If there some other debug information or log that I can check?

Here are the steps I have been following:
- Open the CVS Repositories view in my RTC 2.0 Beta client
- Navigate to my top level folder called "catt", under HEAD
- Right click and select Import into Jazz
- Select import as top-level folders
- Import into a change set archive file
- Keep the change set archive
- filename: /home/jmtaylor/archive.tar
- press Finish

Could it be a compatibility issue with the CVS server? What information would I need to check?


Hello,

Just quick question: Have you read and followed: https://jazz.net/wiki/bin/view/Main/SCMImport ?

kind regards,
Jakub

permanent link
Jeff Taylor (7673) | answered Apr 24 '09, 8:52 a.m.


Hello,

Just quick question: Have you read and followed: https://jazz.net/wiki/bin/view/Main/SCMImport ?

kind regards,
Jakub


Yes, these are the instructions that I have been following. I've tried the change set archive approach and specifying a date range. Both have failed for me.

permanent link
Michael Valenta (3.7k3) | answered Apr 24 '09, 9:30 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
Are there any errors that look related in your log file (which you can
see using the Error Log view in RTC).

Michael

jmtaylor wrote:
jjurkiewiczwrote:

Hello,

Just quick question: Have you read and followed:
https://jazz.net/wiki/bin/view/Main/SCMImport ?
kind regards,
Jakub

Yes, these are the instructions that I have been following. I've tried
the change set archive approach and specifying a date range. Both have
failed for me.

permanent link
Jeff Taylor (7673) | answered Apr 24 '09, 10:36 a.m.
Are there any errors that look related in your log file (which you can
see using the Error Log view in RTC).


Thanks Michael... I knew there had to be more information somewhere.

I have found basically two types of errors. Ther first is the error, the second is a warning that is repeated many times.

Error
-----
A client error occurred while trying to create change set archive /home/jmtaylor/archive.tar

com. ibm.team.repository.common.TeamRe positoryException: A client error occurred while trying to create change set archive /home/jmtaylor/archive.tar
at com.ibm.team.filesystem.ccvs.internal. CVSImporter.createChangeSetArchive(CVSImporter.java:180)
at com.ibm.team.scm.client.importz.internal. CreateArchiveOperation.run(CreateArchiveOperation.java:32)
at com.ibm.team.scm.client.importz.internal. ui.ImportOperation.createArchive(ImportOperation.java:156)
at com.ibm.team.scm.client.importz.internal. ui.ImportOperation.filesystemRun(ImportOperation.java:119)
at com.ibm.team.filesystem.ccvs.ui.internal. CVSImportOperation.filesystemRun(CVSImportOperation.java:114)
at com.ibm.team.filesystem.ui.operations. FileSystemUIOperation.repositoryRun(FileSystemUIOperation.java:4 3)
at com.ibm.team.repository.rcp.ui.op erations.RepositoryOperation.run( RepositoryOperation.java:42 )
at com.ibm.team.repository.rcp.ui.op erations.JobRunner.run(JobRunner. java:205)
at com.ibm.team.repository.rcp.ui.op erations.JobRunner$1.run(JobRunner. java:62)
at org.eclipse.core.internal.jobs.Worker. run(Worker.java:55)
Caused by: org.eclipse.team.internal.ccvs.core. connection.CVSCommunicationException: I/O has been interrupted.
at org.eclipse.team.internal.ccvs.core. connection.Connection.readLine(Connection.java:157)
at org.eclipse.team.internal.ccvs.core. client.Session.readLine(Session.java:300)
at org.eclipse.team.internal.ccvs.core. client.Request.executeRequest(Request.java:145)
at org.eclipse.team.internal.ccvs.core. client.Command.doExecute(Command.java:410)
at org.eclipse.team.internal.ccvs.core. client.Checkout.doExecute(Checkout. java:159)
at org.eclipse.team.internal.ccvs.core. client.Command$1.run(Command.java:329)
at org.eclipse.team.internal.ccvs.core. resources.RemoteFolder.run(RemoteFolder.java:467)
at org.eclipse.team.internal.ccvs.core. client.Command.execute(Command.java:341)
at com.ibm.team.filesystem.ccvs.internal. util.CVSUtil.retryCommand(CVSUtil. java:62)
at com.ibm.team.filesystem.ccvs.internal. CVSImporter.fetchFiles(CVSImporter. java:328)
at com.ibm.team.filesystem.ccvs.internal. CVSImporter.fetchHistory(CVSImporter.java:271)
at com.ibm.team.filesystem.ccvs.internal. CVSImporter.gatherInformation(CVSImporter.java:256)
at com.ibm.team.filesystem.ccvs.internal. CVSImporter.createChangeSetArchive(CVSImporter.java:213)
at com.ibm.team.filesystem.ccvs.internal. CVSImporter.createChangeSetArchive(CVSImporter.java:175)
... 9 more

Warning
-------
CVS file catt/cruisecontrol/config.xml either contains invalid line endings on the server (CR/LF instead of just LF) or is a binary file that is not marked as -kb.

An exception stack trace is not available.

permanent link
Michael Valenta (3.7k3) | answered Apr 24 '09, 2:11 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
I'm not sure why the communications would have been interrupted. At this
stage, I would say the best approach would be to enter a work item
against Source Control in the Rational Team Concert project area of
jazz.net. It could be a server version problem so you should include the
server version you are working with but it could be a number of other
things as well. It would be good to track this in a work item so the
information is not lost once the issue is resolved.

Michael

jmtaylor wrote:
Michael Valentawrote:
Are there any errors that look related in your log file (which you
can
see using the Error Log view in RTC).


Thanks Michael... I knew there had to be more information somewhere.

I have found basically two types of errors. Ther first is the error,
the second is a warning that is repeated many times.

Error
-----
A client error occurred while trying to create change set archive
/home/jmtaylor/archive.tar

com. ibm.team.repository.common.TeamRe positoryException: A client
error occurred while trying to create change set archive
/home/jmtaylor/archive.tar
at com.ibm.team.filesystem.ccvs.internal.
CVSImporter.createChangeSetArchive(CVSImporter.java:180)
at com.ibm.team.scm.client.importz.internal.
CreateArchiveOperation.run(CreateArchiveOperation.java:32)
at com.ibm.team.scm.client.importz.internal.
ui.ImportOperation.createArchive(ImportOperation.java:156)
at com.ibm.team.scm.client.importz.internal.
ui.ImportOperation.filesystemRun(ImportOperation.java:119)
at com.ibm.team.filesystem.ccvs.ui.internal.
CVSImportOperation.filesystemRun(CVSImportOperation.java:114)
at com.ibm.team.filesystem.ui.operations.
FileSystemUIOperation.repositoryRun(FileSystemUIOperation.java:4 3)
at com.ibm.team.repository.rcp.ui.op erations.RepositoryOperation.run(
RepositoryOperation.java:42 )
at com.ibm.team.repository.rcp.ui.op erations.JobRunner.run(JobRunner.
java:205)
at com.ibm.team.repository.rcp.ui.op
erations.JobRunner$1.run(JobRunner. java:62)
at org.eclipse.core.internal.jobs.Worker. run(Worker.java:55)
Caused by: org.eclipse.team.internal.ccvs.core.
connection.CVSCommunicationException: I/O has been interrupted.
at org.eclipse.team.internal.ccvs.core.
connection.Connection.readLine(Connection.java:157)
at org.eclipse.team.internal.ccvs.core.
client.Session.readLine(Session.java:300)
at org.eclipse.team.internal.ccvs.core.
client.Request.executeRequest(Request.java:145)
at org.eclipse.team.internal.ccvs.core.
client.Command.doExecute(Command.java:410)
at org.eclipse.team.internal.ccvs.core.
client.Checkout.doExecute(Checkout. java:159)
at org.eclipse.team.internal.ccvs.core.
client.Command$1.run(Command.java:329)
at org.eclipse.team.internal.ccvs.core.
resources.RemoteFolder.run(RemoteFolder.java:467)
at org.eclipse.team.internal.ccvs.core.
client.Command.execute(Command.java:341)
at com.ibm.team.filesystem.ccvs.internal.
util.CVSUtil.retryCommand(CVSUtil. java:62)
at com.ibm.team.filesystem.ccvs.internal.
CVSImporter.fetchFiles(CVSImporter. java:328)
at com.ibm.team.filesystem.ccvs.internal.
CVSImporter.fetchHistory(CVSImporter.java:271)
at com.ibm.team.filesystem.ccvs.internal.
CVSImporter.gatherInformation(CVSImporter.java:256)
at com.ibm.team.filesystem.ccvs.internal.
CVSImporter.createChangeSetArchive(CVSImporter.java:213)
at com.ibm.team.filesystem.ccvs.internal.
CVSImporter.createChangeSetArchive(CVSImporter.java:175)
.. 9 more

Warning
-------
CVS file catt/cruisecontrol/config.xml either contains invalid line
endings on the server (CR/LF instead of just LF) or is a binary file
that is not marked as -kb.

An exception stack trace is not available.

permanent link
Sandeep Katoch (11) | answered May 14 '09, 6:21 p.m.
Hi,

I had a similar problem with CVS import when I was specifying a date range for import.

Finally (after many many attempts...and finally debugging RTC code, which btw is available for download), I figured out that it was a CVS error.

Then I turned on "Display detailed protocol output to stdout ..." in CVS preferences and got the following error in console:

E cvs [rlog aborted]: Can't parse date/time: Tue May 15 00:00:00 IST 2007


Apparently, CVS did not like the "IST" in the date and kept throwing the error. And RTC client treats this exceptions as "create change set archive" error (I am sure it could do better here to provide the exact cause of error).

So, my CVS repository is around the world for me, and hence the "IST" from my time zone causes it strife.
Solution for me: Changed my time zone to GMT and it works fine now.

In general, I would suggest to turn on CVS "Display detailed protocol..." option to find out the exact cause.

Hope this helps anyone facing these kind of issues.

regards
Sandeep

permanent link
Sandeep Katoch (11) | answered May 15 '09, 7:41 a.m.
Apparently it worked only once. During this time (after I had set my clock to GMT), the time zone being sent to CVS was empty.
From all I could read in CVS docs, it does not expect anything other than UTC in zone information. Hence it worked fine.

After I have restarted eclipse, the CVS command still contains timezone in the form of GMT, which is now causing errors again.

This probably requires a fix in RTC client, to format the date being sent CVS as per CVS expectations.

permanent link
Yusuke Kobayashi (31164) | answered Mar 17 '10, 7:23 a.m.
Hi,

I had a similar problem with CVS import using RTC2.0.0.2.

In my case, the steps I have been following were the same above, but the different error message occured.
Here is the exception:
An internal error occurred during: "Importing from CVS".
!STACK 0
java.lang.IllegalStateException: Contents for testMigration/test/Migration.java, testMigration/.classpath, testMigration/.project, testMigration/test/Messages.java, were not fetched
at com.ibm.team.filesystem.ccvs.internal.CVSImporter.fetchFiles(CVSImporter.java:351)
at com.ibm.team.filesystem.ccvs.internal.CVSImporter.fetchHistory(CVSImporter.java:271)
at com.ibm.team.filesystem.ccvs.internal.CVSImporter.gatherInformation(CVSImporter.java:256)
at com.ibm.team.filesystem.ccvs.internal.CVSImporter.createChangeSetArchive(CVSImporter.java:213)
at com.ibm.team.filesystem.ccvs.internal.CVSImporter.createChangeSetArchive(CVSImporter.java:175)
at com.ibm.team.scm.client.importz.internal.CreateArchiveOperation.run(CreateArchiveOperation.java:32)
at com.ibm.team.scm.client.importz.internal.ui.ImportOperation.createArchive(ImportOperation.java:156)
at com.ibm.team.scm.client.importz.internal.ui.ImportOperation.filesystemRun(ImportOperation.java:119)
at com.ibm.team.filesystem.ccvs.ui.internal.CVSImportOperation.filesystemRun(CVSImportOperation.java:114)
at com.ibm.team.filesystem.ui.operations.FileSystemUIOperation.repositoryRun(FileSystemUIOperation.java:43)
at com.ibm.team.repository.rcp.ui.operations.RepositoryOperation.run(RepositoryOperation.java:42)
at com.ibm.team.repository.rcp.ui.operations.JobRunner.run(JobRunner.java:205)
at com.ibm.team.repository.rcp.ui.operations.JobRunner$1.run(JobRunner.java:62)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

why were not these files fetched?
Is there Any workaround?

Hope this helps anyone facing these kind of issues.

Thanks in advance for your help.

Yusuke

permanent link
Michael Valenta (3.7k3) | answered Mar 17 '10, 9:26 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
I don;t know why the files were not fetched. RTC requested the files
from the CVS server bu they were not provided. My guess is that there is
something in the history of thee files that is confusing the RTC
importer. Can you look at the history of these files? To track this
properly, you should open a work item against the RTC Source Control
component. If you can include a screen shot or, better yet, a log of the
history of the files involved, that would be helpful.

As a work around, you could extract an SVN dump file from your repo
using cvs2svn and then import from that dump file.

Michael

AHA03506 wrote:
Hi,

I had a similar problem with CVS import using RTC2.0.0.2.

In my case, the steps I have been following were the same above, but
the different error message occured.
Here is the exception:
An internal error occurred during: "Importing from CVS".
!STACK 0
java.lang.IllegalStateException: Contents for
testMigration/test/Migration.java, testMigration/.classpath,
testMigration/.project, testMigration/test/Messages.java, were not
fetched
at
com.ibm.team.filesystem.ccvs.internal.CVSImporter.fetchFiles(CVSImporter.java:351)
at
com.ibm.team.filesystem.ccvs.internal.CVSImporter.fetchHistory(CVSImporter.java:271)
at
com.ibm.team.filesystem.ccvs.internal.CVSImporter.gatherInformation(CVSImporter.java:256)
at
com.ibm.team.filesystem.ccvs.internal.CVSImporter.createChangeSetArchive(CVSImporter.java:213)
at
com.ibm.team.filesystem.ccvs.internal.CVSImporter.createChangeSetArchive(CVSImporter.java:175)
at
com.ibm.team.scm.client.importz.internal.CreateArchiveOperation.run(CreateArchiveOperation.java:32)
at
com.ibm.team.scm.client.importz.internal.ui.ImportOperation.createArchive(ImportOperation.java:156)
at
com.ibm.team.scm.client.importz.internal.ui.ImportOperation.filesystemRun(ImportOperation.java:119)
at
com.ibm.team.filesystem.ccvs.ui.internal.CVSImportOperation.filesystemRun(CVSImportOperation.java:114)
at
com.ibm.team.filesystem.ui.operations.FileSystemUIOperation.repositoryRun(FileSystemUIOperation.java:43)
at
com.ibm.team.repository.rcp.ui.operations.RepositoryOperation.run(RepositoryOperation.java:42)
at
com.ibm.team.repository.rcp.ui.operations.JobRunner.run(JobRunner.java:205)
at
com.ibm.team.repository.rcp.ui.operations.JobRunner$1.run(JobRunner.java:62)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

why were not these files fetched?
Is there Any workaround?

Hope this helps anyone facing these kind of issues.

Thanks in advance for your help.

Yusuke

Your answer


Register or to post 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.