This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 72950 - CVS 'Update' errors
Summary: CVS 'Update' errors
Status: RESOLVED WORKSFORME
Alias: None
Product: versioncontrol
Classification: Unclassified
Component: CVS (show other bugs)
Version: 5.x
Hardware: PC Windows ME/2000
: P1 blocker (vote)
Assignee: issues@versioncontrol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-22 18:43 UTC by markjl
Modified: 2007-01-04 17:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description markjl 2006-02-22 18:43:29 UTC 
I had a module checked out of our CVS. On the very top level I did an
'Update'...many files had changed (about 12 I guess). This seemed to go ok
until I tried to compile my code. Many of the files the 'Update' had changed
had errors in them like - 'try' without 'catch' or 'finally' or placing
comments inside parts of functions that sort of thing...many were just garbled.
Anyway, if I change a file and save it and then do CVS - 'Revert Modifications' 
the file comes out of CVS as I would expect. By the way, the files the CVS -
 'Update' changed did not have and local changes.
Comment 1 Peter Pis 2006-02-23 09:53:27 UTC 
This issue seems to be a duplicate of #72948.
Comment 2 markjl 2006-02-23 15:11:22 UTC 
No not at all. In '72948' the update just didn't seem to do anything. It did 
not update at all. In this one, it tried to update the files but it failed. The 
files were all messed up and would no longer compile. This may connected to 
CVS 'Resolve Issues' as I am fairly certain that I had to use it after 
the 'Update' was complete. Keep in mind that at least 12 files were involved in 
this update and I had to resolve issues with at least 3 of them.
Comment 3 _ pkuzel 2006-03-01 11:46:02 UTC 
I guess server sent broken patches or you have modified the files concurrently
with running the update.

Is not it the case?
Comment 4 markjl 2006-03-01 14:08:58 UTC 
Well, I don't know about the server sending broken patches (how would I be able 
to tell?) but I know I definitely DID NOT modify the files during the update.
Comment 5 _ pkuzel 2006-03-01 18:31:05 UTC 
You can run the IDE with -j-DcvsClientLog=C:\tmp\cvs-protocol and then observe
the cvs-protocol.in file content.

Please attach it if you find a reprocase.
Comment 6 _ pkuzel 2006-03-08 18:18:50 UTC 
markjl this is the second "update" issue you reported. I guess that problem
could be caused by your cvs server. What version do you use?

Anyway closing as unreproducible.
Comment 7 markjl 2006-03-08 19:04:15 UTC 
We are using CVS Server v1.11.17 

I must admit that I have not seen this sort of thing happen lately but I'm 
always scared now whenever I execute CVS 'Update...'
Comment 8 _ pkuzel 2006-03-09 08:52:27 UTC 
CVS Server v1.11.17 is very reliable, still it can panic from time to time.