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 Mon, 28 Oct 2002 16:03:04 +0100, "Damien Harper" <harperd at keops.net> wrote: >Hi all, >I'm quite used to use CVS on Linux and I get some troubles making CVSNT work >properly ! >I installed it on a Windows 2000 Server with almost no troubles (just had a >problem with spaces in PATH). >Then: >1. I created a repository and initialized it. >2. I created a module TestCVS : everything went OK >3. I added and commited a text file test.txt (cvs -q -x add test.txt then >cvs -q -x commit -m "blabla" test.txt) : everything went OK >4. I modified and commited it : everything went OK >5. I ran rcsdiff -p --unified=3 -r1.1 -r1.2 "/repository/test.txt,v" : CVSNT >told me that everything is different >6. I modified and commited the file again : everything went OK >7. I ran rcsdiff -p --unified=3 -r1.1 -r1.3 "/repository/test.txt,v" : CO >told me that "edit script refers to line past end of file" then "co aborted" >8. I ran rcsdiff -p --unified=3 -r1.2 -r1.3 "/repository/test.txt,v" : CVSNT >told me that everything is different > >I made EXACTLY the same manipulation on my CVS server on my linux box and >EVERYTHING was OK >So what's the problem ??? Why are there such differences. > It's probably rcsdiff. Does the version of rcsdiff you ran on the NT box work handle CR/LF pairs properly? Presumably rcsdiff tries to modify the file in some way? Are you sure it's making exactly the same modifications (again, taking CR/LF modifications into account)? Running legacy rcs tools against a cvs repository isn't supported, btw. You can seriously screw up a repository that way. Tony