Version: 3.0.90 (using KDE 3.2.2, SuSE) Compiler: gcc version 3.3.1 (SuSE Linux) OS: Linux (i686) release 2.4.21-215-default If I run a cvs update on the entire project tree - for example the if I select the root of the KDevelop CVS image - the update seems to complete correctly. The status displayed in the File Tree widget remains "unknown". If I open the same project in cervisia and do an update, it runs the CVS update without indicating anything is changed, and then displays the local files as up to date. I expect the CVS status displayed in the File Tree to be consistent with that displayed by cervisia. That is not the case.
Hmmm ... that's strange ... I've tried both my local kdevelop CVS copy and some other projects of mine on my local CVS pserver and it works fine ... Can you please build in debug and take a look at kdevelop's output? You should see these lines at first: <snip> kdevelop (file view): VCSFileTreeWidgetImpl::slotSyncWithRepository() kdevelop (file view): VCS Info requested for: . kdevelop (cvs interface): Running command : cvs -f status '.' <... wait for a while until response is got from the remote server and the output should have lines such as the following ...> <snip> kdevelop (file view): Nice! Found info for this file: (AUTHORS, 1.1, 1.1, up-to-date) kdevelop (file view): Widget item filename is: COPYING kdevelop (file view): Nice! Found info for this file: (COPYING, 1.1, 1.1, up-to-date) kdevelop (file view): Widget item filename is: ChangeLog kdevelop (file view): Nice! Found info for this file: (ChangeLog, 1.3, 1.3, up-to-date) <snip> <... or this messages for files it doesn't know ...> kdevelop (file view): Widget item filename is: matrixmathtester.kdevses kdevelop (file view): Map does not contain anything useful about this file ;-( matrixmathtester.kdevses
I've discovered that the 'sync with repository' does cause the relative status of the files to be displayed. I had not been doing that because I am using anonymous read-only access at this point, and I believe that attempts to write to the repository.
"Sync with repository" uses "cvs status" and does not attempts to write anything on the remote server: i've experimented with it playing with a module fetched from anoncvs.kde.org (which uses anonymous read-only access).