rcs 5.7 bug

[Mike MacKenzie]

I've found what I'm pretty sure is a bug in co for rcs 5.7.

Summary:  You can co -l two revisions of a file, but doing a 3rd
confuses co.

If you have two versions of a file checked out and locked, and try to co

-l a
third revision you get a warning about not having specified a revision
number (even though you have), and it tells you you have 3 revisions
locked.  The kicker is that the
third revision is *not* locked; you end up with only the two original
locks.  Even more interesting you do get a working file that is set up
as if there were a lock (owner write
permission and the $Id$ line has a locker field in it.

Here's an example session that demonstrates the error, based on a simple

test file 't', that
has 3 revisions; 1.1 and 1.2 are already locked.

==============================================================================

*KB* ~/test > uname -a
SunOS bell 5.7 Generic_106541-18 sun4u sparc SUNW,Ultra-250

*KB* ~/test > co -V
RCS version 5.7

*KB* ~/test > co -u1.3 t
t,v  -->  t
co: t,v: multiple revisions locked by mmackenz; please specify one
revision 1.3 (unlocked)
done
*KB* ~/test > less t
1
2
3
$Id: t,v 1.3 2002/02/20 21:01:22 mmackenz Exp $

*KB* ~/test > co -l1.3 t
t,v  -->  t
co: t,v: multiple revisions locked by mmackenz; please specify one
revision 1.3 (locked)
co: t,v: warning: You now have 3 locks.
done

*KB* ~/test > rlog t

RCS file: t,v
Working file: t
head: 1.3
branch:
locks: strict
        mmackenz: 1.2
        mmackenz: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 3;     selected revisions: 3
description:
----------------------------
revision 1.3
date: 2002/02/20 21:01:22;  author: mmackenz;  state: Exp;  lines: +2 -1

rev2
----------------------------
revision 1.2    locked by: mmackenz;
date: 2002/02/20 21:01:01;  author: mmackenz;  state: Exp;  lines: +2 -1

rev1
----------------------------
revision 1.1    locked by: mmackenz;
date: 2002/02/20 21:00:32;  author: mmackenz;  state: Exp;
Initial revision
=============================================================================

*KB* ~/test > ls -l
total 2
-rw-r--r--   1 mmackenz other          62 Feb 20 16:11 t
-r--r--r--   1 mmackenz other         561 Feb 20 16:02 t,v

*KB* ~/test > cat t
1
2
3
$Id: t,v 1.3 2002/02/20 21:01:22 mmackenz Exp mmackenz $

==========================================================================

If anyone wants to replicate this, Here is the ,v file before this test
session above began:

====================================
head    1.3;
access;
symbols;
locks
        mmackenz:1.2
        mmackenz:1.1; strict;
comment @# @;


1.3
date    2002.02.20.21.01.22;    author mmackenz;        state Exp;
branches;
next    1.2;

1.2
date    2002.02.20.21.01.01;    author mmackenz;        state Exp;
branches;
next    1.1;

1.1
date    2002.02.20.21.00.32;    author mmackenz;        state Exp;
branches;
next    ;


desc
@@


1.3
log
@rev2
@
text
@1
2
3
$Id: t,v 1.2 2002/02/20 21:01:01 mmackenz Exp mmackenz $@


1.2
log
@rev1
@
text
@d3 2
a4 1
$Id: t,v 1.1 2002/02/20 21:00:32 mmackenz Exp mmackenz $@


1.1
log
@Initial revision
@
text
@d2 2
a3 1
$Id$@
==========================================================

Thnaks,

Mike MacKenzie