Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
On Sat, 04 Feb 2006 02:01:29 +0000, Tony Hoyle <tony.hoyle at march-hare.com> wrote: >Randy McCharles wrote: >> Can anyone recommend a tool to verify RCS integrity of CVS ,v files? >> >> We have a few "unexpected EOF" errors reported by viewcvs, but the python backtrack doesn't tell us where in the file the problem is. >> Since cvs checks out the files no problem, I have to think this is a minor syntax error in the history information somewhere that can be corrected if I know the line #. I hate to lose all the history but deleting/re-adding the files as rev 1.1 >> >> That said, it would be handy to periodically run an integrity-check of entire repositories from time to time. >> >If cvs is checking the files out OK then the problem probably lies in >viewcvs... viewcvs hasn't accessed the rcs files directly for a while >now (doesn't work very well with the updated formats.. that's why cvsnt >has rcs functions). > >I'm sure there is a way of getting a better backtrace but that's more >python territory and I'm no expert.. Bo? > To get a better error output you can edit the file viewcvs/lib/debug.py and change one line as follows: SHOW_CHILD_PROCESSES = 0 to SHOW_CHILD_PROCESSES = 1 If you now access the file with a problem through ViewCvs there will be a rather lengthy error and debug report. This can be either analyzed yourself or sent to the vievc list for help. Viewcvs changed its name to viewvc a while back and it also changed its server. The homepage is now here: http://www.viewvc.org/ You can find links to its mail list subscription here: http://viewvc.tigris.org/servlets/ProjectMailingListList /Bo (Bo Berglund, developer in Sweden)