Path: utzoo!attcan!uunet!munnari!otc!metro!ipso!stcns3!stca77!paul
From: paul@stca77.stc.oz (Paul McCaughey)
Newsgroups: comp.unix.xenix
Subject: Bug in SCCS delta command.
Message-ID: <266@stca77.stc.oz>
Date: 5 Sep 88 02:09:20 GMT
Reply-To: paul@stca77.stc.oz (Paul McCaughey)
Organization: Alcatel-STC, Alexandria, AUSTRALIA
Lines: 45


	I have just discovered a bug in the SCCS delta command. When
we make a new release, we update the SCCS release number by a applying
commands similar to:

	get -r4 s.filename
	delta -y"comment" s.filename

for each file. (Our current release happens to be 4). This normally works
happily, except that this time some of the files weren't at release 3,
so delta attempts to insert null deltas for release 2 and 3. It does not,
however do this properly. This is what the s-file looks like:

^Ah34974
^As 00000/00000/00113
^Ad D 4.1 88/09/02 18:21:06 paul 4 3
^Ac Release 4
^Ae
r (cm1)^Ad D 3.1 88/09/02 18:21:06 paul 3 2
^Ac AUTO NULL DELTA
^Ae
r (cm1)^Ad D 2.1 88/09/02 18:21:06 paul 2 1
^Ac AUTO NULL DELTA
^Ae
^As 00113/00000/00000
^Ad D 1.1 88/01/08 10:31:45 peter 1 0
^Ac date and time created 88/08/01 10:31:45 by peter
^Ae
etc..

As you can see, the "^Ad" lines are preceded by part of an error message
(invalid key letter), and the "^As" lines are missing from the null deltas.
This causes any other SCCS utilities to complain about invalid format
in line 6. I patched the files by removing the "r (cm1)" and copying
the first ^As line to the two null deltas. I then applied admin -z to fix
the checksum and all is happy again. 

Our configuration is SCO Xenix Sys V 2.2.1, on an 80286 machine.

Does anyone know of any fixes for this? (apart from not attempting
the ridiculous in the first place).
-- 
Paul McCaughey	            paul@stca77.stc.oz
Alcatel STC Australia       ...uunet!munnari!stca77.stc.oz!paul
+61 2 690 5245              paul%stca77.stc.oz@uunet.UU.NET