Apache OpenOffice (AOO) Bugzilla – Issue 914
CVS history log is corrupted
Last modified: 2003-12-06 14:52:32 UTC
If you cvs checkout the following file at the tip of the tree: sal/systools/win32/comdlg32/comdlg9X.cxx I get the following error: Terminate on signal 11 Whereas if I check this file out at using the -rSRC627 tag, I get a successful checkout. I have prioritized this error as a P1 because no one can checkout the sal module due to this problem. I have to conclude that during the commit of revision 1.3 of the file (a cvs remove), the CVS repository's log files got corrupted. I tried committing a second cvs remove on this file. However, the behavior has not changed. Can you take a look at this file and see if the CVS repository's log and RCS files can be syncronized. The last version committed (the cvs remove) was version 1.3 on May 10, 2001. Thanks, Patrick
Assigning to Kat as primary tech support. Kat, please investigate and summarize findings here.
Accepting this issue for investigation and starting the internal process for resolution. Kat
In addition, it looks like one of the CVS mirrors is stuck as a result of this problem. Any cvs updates of the sal/systools/win32/comdlg32 directory show that the CVS user "tigrisc" has had it locked for 1.5 hours now.
Correction: there was a typo in my original posting. The correct file name that is corrupted is: sal/systools/win32/comdlg32/comdlgw9X.cxx Note that "w" in the filename. All of information is the same: version 1.3 is the latest valid version. All of the later revisions (1.4 and 1.5) should be ignored as they were only my attempts to get CVS to "correct" itself. Thanks, Patrick
Hi, An engineer here removed the lock files. These were likely caused by a commit not successfully being completed. Could you please attempt another checkout of the trunk and let me know what, if any messages you receive. Thank you, Kat
When executing the following command: cd sal/systools/win32/comdlg32 ; cvs update -A I get the following output: U ConvertOfn.c U ConvertOfn.h U GetOpenFileName.c U GetOpenFileName.h U GetSaveFileName.c U GetSaveFileName.h cvs server: nothing known about comdlg9X.cxx U makefile.mk Unfortunately, the above output shows that some part of the CVS repository thinks that a "comdlg9X.cxx" exists but something is missing. Strangely, if I execute the following command: cvs log comdlg9X.cxx I get the following output: RCS file: /cvs/porting/sal/systools/win32/comdlg32/comdlg9X.cxx,v Working file: comdlg9X.cxx head: branch: locks: strict access list: symbolic names: keyword substitution: kv total revisions: 0; selected revisions: 0 description: As you can see, no versions are listed. Maybe the RCS file has been deleted on the CVS server? As for comdlgw9X.cxx, I have checked in a copy of version 1.3 at the tip of the tree (version 1.6). So this file is now OK.
The issue regarding the comdlg9 x.cxx file is being worked on and I will keep you updated of its progress. I am reducing the priority on this issue though because the main problem of not being able to check out the sal module has been resolved. Thank you, Kat
Actually, the "Terminate on signal 11" kills a checkout of sal. So, this problem is still not resolved. This needs to be resolved hopefully by early tomorrow before the next syncing of the CVS mirrors. Thanks, Patrick
I was able to checkout the sal module just now without receiving a signal 11. What options are you using and are you downloading from the main OOo server? Thank you Kat
I am use the following command to checkout sal: cvs co -D "05/16/2001" sal Apparently, this problem only shows up with the -D (date tag) option. Thanks, Patrick
The comdlg9x.cxx file has been moved out of the way by one of our engineers. I was able to perform a succesful checkout by date. Could you please try a fresh checkout of the sal module as well and report your results? Thank you Kat
This works perfectly now so I am changing the issue to "resolved". Thanks for taking care of this.
As agreed by Louis I will close these resolved fixed kat (support)-owned issues now. If you have trouble with that, please re-open the issue.