The "co -ko" or "rcs -ko" commands will fix this.
Original message :
I've run into an anomoly using RCS to manage Oracle Forms files.
The form is developed on a PC and uploaded to a Compaq Tru64 v4.0e system
for ci. When the file is co'd and compiled
the compile fails due to a corrupted file.
Versions :
OS : Compaq Tru64 UNIX v4.0e + pk3
RCS: Shipped with OS Installed from GNU sources
ci v1.1.9.2 v5.3
co v1.1.9.2 v5.2
gnudiff 1.15 GNU diffutils version 2.7-gnupro-98r2
Interestingly enough, the rcs shipped with the OS uses the
gnu diff that is kept in /usr/lbin rather than the "normal" diff in
/usr/bin.
Here is a script of the process that illustrates the problem :
$ cp TINVMUP.fmb.good test.file
$ sum *.good test.file
46575 272 TINVMUP.fmb.good
46575 272 test.file
$ ci test.file
test.file,v <-- test.file
enter description, terminated with single '.' or end of file:
NOTE: This is NOT the log message!
>> test
>> .
initial revision: 1.1
done
$ which co
/usr/local/bin/co
$ co -l test.file
test.file,v --> test.file
revision 1.1 (locked)
done
$ sum *.good test.file
46575 272 TINVMUP.fmb.good
43592 273 test.file
I had assumed that the old versions were the problem, but
the newer version also does it.
I originally tested binary file ci/co using a jpeg graphics
file with no problems displaying the resulting files.
Any ideas on where to start debugging this?
Alan Davis
alan.c.davis_at_att.net
-----
Alan C. Davis
Technology Services
davis_at_tessco.com
Received on Fri Jan 14 2000 - 22:48:03 NZDT