Community
Participate
Working Groups
Using extssh to connect to the repository, all incomming changes are collected under "Unassigned Remote Changes". When I use pserver, all works fine.
Hello, I have this problem with both extssh and pserver modes. I am using 3.1M4 under linux/gtk.
Sylvain, A collegue of mine suggest that under linux/gtk the button "Show Change Sets", in the synchonize view toolbar, is by default not visible. This button can be shown by resizing the synchronize view. When you use pserver, pushing this button results in grouping the incomming changes by Change Set. Roel
Hi, This button is visible even on linux/gtk. (However, is is enabled only in incoming mode [new feature since 3.1M2]). You can see on the attached screenshot. Cheers, Sylvain
Created attachment 16906 [details] Screenshot showing the "show change set" button
What CVS server version are you using. The grouped change sets is based on being able to parse the logs.
Concurrent Versions System (CVS) 1.11.5 (client/server)
using version 1.11.1 (debian woody). I wanted to test version 1.12.9 on my local machine through pserver, but I got an exception when I did the update: Error 2005-01-06 09:25:02.217 An internal error occurred during: "Synchronize View: Processing label changes". java.lang.NullPointerException at java.util.Calendar.setTime(Calendar.java:1032) at java.text.SimpleDateFormat.format(SimpleDateFormat.java:785) at java.text.SimpleDateFormat.format(SimpleDateFormat.java:778) at java.text.DateFormat.format(DateFormat.java:314) at org.eclipse.team.internal.ccvs.ui.subscriber.CVSChangeSetCollector$CVSCheckedInChangeSet.<init>(CVSChangeSetCollector.java:109) at org.eclipse.team.internal.ccvs.ui.subscriber.CVSChangeSetCollector.createChangeSetFor(CVSChangeSetCollector.java:368) at org.eclipse.team.internal.ccvs.ui.subscriber.CVSChangeSetCollector.addRemoteChange(CVSChangeSetCollector.java:338) at org.eclipse.team.internal.ccvs.ui.subscriber.CVSChangeSetCollector.addSingleRevision(CVSChangeSetCollector.java:285) at org.eclipse.team.internal.ccvs.ui.subscriber.CVSChangeSetCollector.addSyncInfoToCommentNode(CVSChangeSetCollector.java:252) at org.eclipse.team.internal.ccvs.ui.subscriber.CVSChangeSetCollector.addLogEntries(CVSChangeSetCollector.java:230) at org.eclipse.team.internal.ccvs.ui.subscriber.CVSChangeSetCollector.access$0(CVSChangeSetCollector.java:225) at org.eclipse.team.internal.ccvs.ui.subscriber.CVSChangeSetCollector$2.run(CVSChangeSetCollector.java:216) at org.eclipse.team.internal.ui.synchronize.SynchronizeModelUpdateHandler$8.run(SynchronizeModelUpdateHandler.java:659) at org.eclipse.team.internal.ui.synchronize.SynchronizeModelUpdateHandler$RunnableEvent.run(SynchronizeModelUpdateHandler.java:125) at org.eclipse.team.internal.ui.synchronize.SynchronizeModelUpdateHandler.executeRunnable(SynchronizeModelUpdateHandler.java:705) at org.eclipse.team.internal.ui.synchronize.SynchronizeModelUpdateHandler.processEvent(SynchronizeModelUpdateHandler.java:218) at org.eclipse.team.internal.core.BackgroundEventHandler.processEvents(BackgroundEventHandler.java:310) at org.eclipse.team.internal.core.BackgroundEventHandler$1.run(BackgroundEventHandler.java:154) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
Roel, could you follow the steps in this URL to get a trace of the communications between the server and client. http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm- home/docs/online/cvs_features2.0/cvs-faq.html#misc_0 This will should us what the rlog command is getting from the server. Ideally, if you could do it for both extssh and pserver, we could more easily pinpoint the difference. P.S. I'm moving this to the REMIND bucket to await your respone.
Trace logs for both pserver and extssh created.
Created attachment 17028 [details] Log of Eclipse Synchronize on pserver As requested
Created attachment 17029 [details] Log of Eclipse Synchronize on extssh As requested
The problem is that your two repositories are different versions. The rlog command is using an option (-S) trhat is supported in 1.11.5 (your pserver repository) but not is 1.11.1p1 (your extssh repository). If you want to use change logs with your extssh repository, you will need to upgrade it. YOu probably should anyway since there have been important security fixes made in the latest 1.11 releases.
Does it make sense let the client have knowledge of the remote cvs version, and adapt its parameter accordingly ? Actually, I have to work with some remote cvs servers, and I don't have the ability to tell the admin to update them. I think this problem could happen to other people too. Or why not have a check on the cvs remote version (maybe at startup), and warn the user that he should update its version, to prevent problems (and to avoid people filling bugzilla with duplicates of this bug) ?
What you suggest makes sense bot involves a fair amount of work. We do not have the manpower to do this (unless you want to provide a patch;-).
Upgrading from 1.11.1p1 to 1.11.5 worked. Thank you for your suggestion. The reason we still used 1.11.1p1 is that that is the version provided with Debian stable.
I've added the entry to the FAQ
Verified