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, 29 Jan 2005 10:26:39 +0100, Bo Berglund <bo.berglund at telia.com> wrote: > >More info: >I took the command that ViewCvs uses and shortened it to a single >file. Then I executed it on the command line myself. Result from two >different files, the first has had a revision committed by build 1863 >and the second is still revision 1.1 which was committed when the >server was 2.0.38: > >C:\>"C:\Programs\cvsnt\cvs.exe" "rcsfile" "rlog" "-r" >"C:\cvsrepo\pc\CVSNT\cvsbin\co.exe,v" >cvs.exe [rcsfile aborted]: unrecognized operation '\x0' >in C:\cvsrepo\pc\CVSNT\cvsbin\co.exe,v > > > >C:\>"C:\Programs\cvsnt\cvs.exe" "rcsfile" "rlog" "-r" >"C:\cvsrepo\pc\CVSNT\cvsbin\ca.pem,v" > >RCS file: C:\cvsrepo\pc\CVSNT\cvsbin\ca.pem,v >Working file: ca.pem >head: 1.1 >branch: >locks: strict >access list: >symbolic names: > CVSNT_2-0-62-1860: 1.1 > CVSNT_2-0-62-1852: 1.1 >keyword substitution: kv >total revisions: 1; selected revisions: 1 >description: >---------------------------- >revision 1.1 >date: 2005/01/19 15:25:10; author: bosse; state: Exp; >Managing the Innosetup installer through my own CVS server. >Now adding current state, which is 2.0.62.1852 >============================================================================= > >Looks like the rcs handling has broken... > I am going to try attaching the co.exe,v file now so that you can check it out. If you use this RCS file when testing the command out you may find out what is going wrong. /Bo (Bo Berglund, developer in Sweden)