| Date Of Receipt: 12-JUL-1995 13:43:49.39
From: SMURF::FLUME::"ode@rust.zso.dec.D5NET.dec.com"
To: FLUME::jmf (Joshua M. Friedman OSF/UNIX SDE 12-Jul-1995 0952)
CC: decwet::ode, flume::tea, flume::odehelp, ode@DEC:.zko.flume
Subj: Re: mkrcs: ci error: no lock set by devrcs
Please provide more information. All we can tell from this is what the error
message says: There was no lock established for the file(s) in question.
------- Included Message
Return-Path: FLUME::jmf
Received: from DECnet-Mail11.slugbt.zso.dec.com by slugbt.zso.dec.com; (5.65/DECwest-OSF-Nov-11-93)
Date: Wed, 12 Jul 1995 06:52:15 -0700
Message-Id: <9507121352.AA20230@slugbt.zso.dec.com>
From: FLUME::jmf (Joshua M. Friedman OSF/UNIX SDE 12-Jul-1995 0952)
To: decwet::ode
Cc: flume::tea, flume::odehelp
Subject: mkrcs: ci error: no lock set by devrcs
Paul, this is a question for DECwest - fwd'd...
Clearly it wasn't related to the /dev/null bug which I fixe & ptt'd.
This error indicates that some of "rcs -l" commands which precede "ci"
are failing.
-josh
------- Forwarded Message
To: jmf@tlaser.zk3.dec.com
Cc: hantman@tlaser.zk3.dec.com
Subject: mkrcs
Date: Wed, 12 Jul 95 09:29:54 -0400
From: hantman@tlaser.zk3.dec.com
X-Mts: smtp
Hi,
I'm still getting the ci error. An example is shown below:
./batch/control/remote_console.exp,v --> ./batch/control/remote_console.exp
revision 3.2
done
./batch/control/remote_console.exp,v <-- ./batch/control/remote_console.exp
ci error: no lock set by devrcs
./batch/control/remote_console_root.exp,v --> ./batch/control/remote_console_
r
oot.exp
revision 3.1
done
./batch/control/remote_console_root.exp,v <-- ./batch/control/remote_console_
r
oot.exp
ci error: no lock set by devrcs
What is this telling me? Can I set AUTHCOVER_DEBUG to get more information back
from mkrcs? Do I need to be worried about this?
- -Paul
------- End of Forwarded Message
|