[Looks like a bug since it is giving an "RCS file internal error" sort
of message.

Also reported by Jeffrey S. Haemer at qms.com and Eric Postpischil of
sky.com.

-kingdon]

To: info-cvs@gnu.org
Sender: monnier@tequila.cs.yale.edu
From: Stefan Monnier <monnier+lists/cvs/news/@tequila.cs.yale.edu>
Subject: problems with symlinks
Date: 23 Nov 1998 15:49:32 -0500

I know very well that symlinks are not supported by CVS, but this still
looks like a bug to me since it ends up messing up the RCS file:

If you turn an existing file into a symlink (in your sandbox) and try to commit
it, CVS (version 1.10.2) happily accepts it, but the resulting RCS file
seems not to be correct.

    ~/tmp-0% mkdir test
    ~/tmp-0% cd test/
    tmp/test-0% echo hello >foo
    tmp/test-0% cvs import -m '' test VENDOR v1 
    N test/foo
    
    No conflicts created by this import
    
    tmp/test-0% cd ..
    ~/tmp-0% rm -rf test
    ~/tmp-0% cvs co test
    U test/foo
    ~/tmp-0% cd test
    tmp/test-1% rm foo           
    tmp/test-0% echo toto >foo.new
    tmp/test-0% ln -s foo.new foo
    tmp/test-0% cvs commit -m '' foo
    Checking in foo;
    /home/monnier/cvsroot/test/foo,v  <--  foo
    new revision: 1.2; previous revision: 1.1
    done
    tmp/test-0% cd ..
    ~/tmp-0% rm -rf test       
    ~/tmp-0% cvs co -r 1.1 test
    cvs [checkout aborted]: invalid change text in /home/monnier/cvsroot/test/foo,v
    ~/tmp-1% cvs -v
    
    Concurrent Versions System (CVS) 1.10.2 (client/server)
    
    Copyright (c) 1989-1998 Brian Berliner, david d `zoo' zuhn, 
 			    Jeff Polk, and other authors
    
    CVS may be copied only under the terms of the GNU General Public License,
    a copy of which can be found with the CVS distribution kit.
    
    Specify the --help option for further information about CVS
    ~/tmp-0% 


-- Stefan