| Date Of Receipt: 19-JUL-1993 16:09:51.81
From: WASTED::jmf "Joshua M. Friedman ULTRIX SDE 19-Jul-1993 1609"
To: rhf@unx.dec.com
CC: mik@unx.dec.com, odehelp@wasted:zko.dec
Subj: re: Can't bsubmit dumptape.c or dump.msg
Bob, what you'll need to do is recreate the file entries by hand in at
least your sandbox's src/.BCSconfig file and maybe also the file
src/.BCSset-Robert_Frey_<setname>
The format in each file must be exactly correct or you'll run into errors.
In the .BCSset* file, the format is one file per line, as a dot-relative
path starting below src, with no extra whitespace or blank lines, i.e.:
./usr/sbin/dump/dump.msg
./usr/sbin/dump/dumptape.c
The format of the .BCSconfig file is similar, but contains rcs
filenames (,v appended), followed by a <tab> and a rev number, and in
fact is identical to the format of the backing trees' logs/SNAPSHOT
file. Careful to have a <tab> and not spaces. The rev numbers are the
rev numbers of the files in the release stream that you started with.
For example, the most recent versions of these files in sterling, as
listed in /usr/sde/osf1/build/agosminor/logs/SNAPSHOT, is as follows.
You can look in the header of the files to see the versions you started
with -- careful to take the AGOSMINOR revs, 4.2.4.* and 4.2.5*
respectively, not the Robert_Frey revs. For eg, if you did a bco of
these two files now backed by agosminor, your .BCSconfig file would
contain these two lines:
./usr/sbin/dump/dump.msg,v 4.2.4.2
./usr/sbin/dump/dumptape.c,v 4.2.5.3
You should be able to reconstruct these entries, after which you'll be
ok. These revs represent the "common ancestor" and are used to determine
if a merge needs to occur, and if so what revs to base the merge on.
-josh
------- Forwarded Message
Return-Path: rhf@unx.dec.com
Received: by locore.zk3.dec.com (5.65/DEC-USSG-ZK3-ULTRIX-09/27/91);
id AA00416; Mon, 19 Jul 1993 14:19:22 -0400
Received: by archie.unx.dec.com; id AA01893; Mon, 19 Jul 1993 14:19:22 -0400
Message-Id: <9307191819.AA01893@archie.unx.dec.com>
To: odehelp@zk3.dec.com
Cc: mik@unx.dec.com, rhf@unx.dec.com
Subject: Can't bsubmit dumptape.c or dump.msg
Date: Mon, 19 Jul 93 14:19:22 -0400
From: rhf@unx.dec.com
X-Mts: smtp
To Whom It May Concern:
I'm unable to bsubmit either dumptape.c or dump.msg. Keep getting the following
message:
>> FATAL ERROR in /usr/sde/ode2.0/tools/alpha_ace/bin/ode/bsubmit:
>> No information for file in .BCSconfig file.
>> File: './usr/sbin/dump/dumptape.c'
Please take appropriate steps and run bsubmit again.
- - No work has been done for this submission.
- - No files have been changed in any way.
- - The files in this submission are not held.
- - The use of the -resub option is not required and will not be recognized.
The original sandbox got destroyed and it was necessary to create a new one.
The state of the destroyed sandbox was that I had finished checking in two
files: dumptape.c and dump.msg. I composed an srequest and obtained a defect
number. Then the original sandbox somehow during the downloading of a new OSF/1
operating system was forever deleted! I then created a new one and checked out
the two files and then, seeing that the files were in the proper state for
checking in, I bcied both from the new sandbox. I then got a ticket number
after the new sandbox was in operation. Naturally, I tried to bsubmit both
files. And that brings me to the current delemma.
What am I to do?
Inquisitively yours,
Bob Frey
------- End of Forwarded Message
|