Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!ginosko!uunet!mcsun!ukc!edcastle!hwcs!zen!vic
From: vic@zen.co.uk (Victor Gavin)
Newsgroups: comp.sys.hp
Subject: Bugs in RCS ??
Keywords: RCS ci bugs
Message-ID: <1730@zen.co.uk>
Date: 12 Oct 89 15:16:48 GMT
Organization: Zengrange Limited, Leeds, England
Lines: 49

[`uname -a` == "HP-UX zen A.B3.10 D 9000/840 5067"]

When using RCS, I have come across the following bugs which others may
like to know about so that they can avoid them.

1) If you have a central RCS directory somewhere, which has many links
to it, and you check a file out as locked in one of the directories
with a link, you can also check it out as locked in a totally
different directory, as long as there isn't a copy of the file in the
second directory.

ie The locking doesn't work, as it is dependent upon having a
writeable copy of the file in the current directory.

2) If you have a file checked out as locked, but which hasn't been
modified, when you check it in it will ask

	File blip is unchanged with respect to revision 1.1
	checkin anyway? [ny](n): 

and if you answer `n', the source file will get *deleted*. Worse still
the lock will still be set so you cannot check out anymore locked
versions.


........
As an aside, maybe someone from HP would like to comment on why some
of the products they ship are much older versions of those available
from other manufacturers (in this case, RCS from HP is dated May 1983,
and there are certainly much newer versions available).


And as a wish, can't we have some more useful stuff available on the
contrib tape.

F'rinstances:

  *) a complete set of compiled and ``working'' GNU stuff,
  *) commands which are non-supported but available on other machines
     eg rdump/rrestore, rpc.lockd, compact etc.
  *) anything else that is executable :-)


			vic
--
Victor Gavin						Zengrange Limited
vic@zen.co.uk						Greenfield Road
..!mcvax!ukc!zen.co.uk!vic				Leeds England
+44 532 489048						LS9 8DB