Version: (using KDE KDE 3.2.1) Installed from: Gentoo Packages OS: Linux If you perform an Update on a modified file and it fails (eg. because CVS couldn't connect to the server), the file's status is changed to "Up to date" even though it isn't.
Hi Paul, thanks for your report. This issue is caused by an inconsistency of CVS. The command cvs returns 0 on success else 1. But there is one exception, if cvs finds a conflict it returns 1 too. So Cervisia handles 0 and 1 as successful execution. I don't know how to solve this in Cervisia right now.
*** Bug 100853 has been marked as a duplicate of this bug. ***
Maybe we can retrieve and remember the correct status of the execution in UpdateView::processUpdateLine()? Similar to what we have in ProgressDialog::processOutput().
Here's another example of the same failure on committing: cvs -f commit -l -m 'xxx' 'path/to/file' 2>&1 ssh_exchange_identification: Connection closed by remote host cvs [commit aborted]: end of file from server (consult above messages if any) [Exited with status 1]
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.