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 email@example.com.
Xavier -- Please keep OSS questions on the list. > head 1.2; access; symbols; locks; strict; comment @# @;expand @b@; > 1.2 date 2005.10.24.16.30.10; author vicente; state dead; > branches; next 1.1; deltatype text; permissions > 444; commitid > 484435d0c111176; kopt ?; filename Image0109.bmp; That's the same problem I saw before -- the "kopt ?;" is causing the problem. It was a binary then removed, and for some reason the server set the expansion flags as "?". Two options moving forward: Patch the server so it defaults ? to something else or otherwise tolerates "?" for expansion flag, or manually fix all your RCS files. If you can work out how to repeat this problem it would be helpful. I tried a couple cases with CVS 1.12.13 and CVSNT 2.5.03 and can't get it to insert a ? for the kopt. I suspect it might be a problem when the file gets converted to CVSNT format since CVS 1.x stores only a single kopt and CVSNT versions them, but again I can't repeat it. Regards, -- Glen Starrett Technical Account Manager, North America March Hare Software, LLC http://march-hare.com/cvspro/ > -----Original Message----- > From: xavier [mailto:xsure at icarvision.com] > > Hi Glen, > > >Run a server trace to see which file is causing the problem, > then take a > >peek in the RCS file. What is the situation? > > That's a piece of the first file which crashes, but there are > many of them: > > head 1.2; access; symbols; locks; strict; comment @# @;expand @b@; > 1.2 date 2005.10.24.16.30.10; author vicente; state dead; > branches; next 1.1; deltatype text; permissions > 444; commitid > 484435d0c111176; kopt ?; filename Image0109.bmp; > 1.1 date 2005.10.19.16.02.53; author vicente; state > Exp; branches; > next ; deltatype text; permissions 666; commitid > 64443566e2475d0; kopt b; filename Image0109.bmp; > [...] > > The problem is how to solve it. > Thanks for the help, and I'm still working on it to make it > work perfect. > Regards, > > Xavier > >