Community
Participate
Working Groups
When setting up a server, one might forget to install cvs :-) The problem is that Eclipse has rather cryptic error messages in this case: This is the error message from the command line cvs on the client: bash: cvs: command not found cvs [checkout aborted]: end of file from server (consult above messages if any) From Eclipse CVS, much more cryptic: ---- Unknown response received from cvs server: org.eclipse.team.internal.ccvs.core.CVSException: Unknown response received from cvs server: at org.eclipse.team.internal.ccvs.core.client.Request.executeRequest(Request.java:222) at org.eclipse.team.internal.ccvs.core.client.ValidRequests.execute(ValidRequests.java:26) at org.eclipse.team.internal.ccvs.core.client.Session.open(Session.java:174) at org.eclipse.team.internal.ccvs.core.resources.RemoteFolderMemberFetcher.performUpdate(RemoteFolderMemberFetcher.java:97) at org.eclipse.team.internal.ccvs.ui.operations.FetchMembersOperation$InternalRemoteFolderMemberFetcher.performUpdate(FetchMembersOperation.java:69) at org.eclipse.team.internal.ccvs.core.resources.RemoteFolderMemberFetcher.fetchMembers(RemoteFolderMemberFetcher.java:64) at org.eclipse.team.internal.ccvs.core.resources.RemoteFolderMemberFetcher.fetchMembers(RemoteFolderMemberFetcher.java:55) at org.eclipse.team.internal.ccvs.ui.operations.FetchMembersOperation.execute(FetchMembersOperation.java:107) at org.eclipse.team.internal.ccvs.ui.operations.CVSOperation.run(CVSOperation.java:81) at org.eclipse.team.internal.ccvs.ui.model.CVSTagElement.fetchDeferredChildren(CVSTagElement.java:136) at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:196) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
I assume you are using the extssh connection method since pserver would have failed authentication instead of failing in the ValidRequests handler. We would need to modify the handler to continue reading from the stream on a failure in order to print all the incoming information. Given that this failure is rare and the amoutn of work we already have queued up for 3.3 is large, I'll have to defer it to a later release. However, we are happy to accept patches.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
