Conference smurf::buildhelp

1011.0. "Re: bsubmit error message - solution" by SMURF::FILTER (Automatic Posting Software - mail to flume::puck) Tue Oct 18 1994 19:52

Date Of Receipt: 	18-OCT-1994 18:02:45.57
From: 	FLAMBE::jmf "Joshua M. Friedman OSF/UNIX SDE"
To: 	[email protected], [email protected]
CC: 	[email protected]
Subj: 	Re:  bsubmit error message - solution

Charlie, here's what you need to do.  ODE thinks that it created
a set called <principal_name>_<set_name>, where <principal_name>
is "Charlie_Franks", and your <set_name>, rather than just "hpaq635d0_v20",
is the full "Charles_Franks_hpaq635d0_v20", since your PRINCIPAL didn't
agree with what your default setname had as a principal name.  This
arose when you changed your name, but still had stuff checked out.

If you do a blog, you'll see that your branch name in rcs is:
	    Charlie_Franks_Charles_Franks_hpaq635d0_v20: 1.2.12

Do the following:
    setenv PRINCIPAL Charlie_Franks
    kinit Charlie_Franks

    Put back the file names as they were:
	.BCSlog-Charlie_Franks_Charles_Franks_hpaq635d0_v20
	.BCSset-Charlie_Franks_Charles_Franks_hpaq635d0_v20

Now do the workon, specifying the (bogus) setname in full:

	workon -sb hpaq635d0_v20 Charles_Franks_hpaq635d0_v20

After your submit and outdate is completed, the .BCS files will 
be removed.  After this, change your PRINCIPAL and ticket back to
Charles_Franks for all future transactions and you'll be all set.

-josh



From [email protected]  Tue Oct 18 16:27:27 1994
Delivery-Date: Tue, 18 Oct 94 16:28:00 -0400
Return-Path: [email protected]
Received: from decvax.zk3.dec.com by flambe.zk3.dec.com; (5.65/1.1.8.2/30Mar94-0502PM)
	id AA17867; Tue, 18 Oct 1994 16:27:27 -0400
Received: from admamy.zk3.dec.com by decvax.dec.com (5.65/DEC-ULTRIX-8/19/92)
	id AA24471; Tue, 18 Oct 1994 16:27:24 -0400
Received: from localhost by admamy.zk3.dec.com; (5.65/1.1.8.2/09Sep94-0232PM)
	id AA01976; Tue, 18 Oct 1994 16:30:30 -0400
Message-Id: <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: bsubmit error message 
Date: Tue, 18 Oct 94 16:30:23 -0400
From: [email protected]
X-Mts: smtp

Hi.

I am attempting a bsubmit of the file ./clients/xterm/charproc.c
from sandbox "hpaq635d0_v20", which is backed by v20supportx.nightly,
and get the following error message:

*** VALIDATION FAILURE ***

./clients/xterm/charproc.c -- not in set.

I believe the problem may stem from the fact that this is
an older sandbox, and I think I had a different Principal
name when it was set up.  My current PRINCIPAL is Charlie_Franks,
but I believe it used to be Charles_Franks.  The file,
rc_files/sets shows the following:

	default Charles_Franks_hpaq635d0_v20
	set Charles_Franks_hpa1635d0_v20 .

The .BCS files in /src were named:

.BCSlog-Charlie_Franks_Charles_Franks_hpaq635d0_v20
.BCSset-Charlie_Franks_Charles_Franks_hpaq635d0_v20

(I thought it odd the name had both Charlie and Charles)

and the .BCSset file did contain the expected file I was attempting
to bsubmit:

.clients/xterm/charproc.c

So, assuming I had screwed things up by changing my Principal between
the time the sandbox was created and the time I did my srequest, I
tried renaming the .BCSlog and .BCSset files to remove the "Charles_Franks"
part, and tried changing the rc_files/sets file to contain "Charlie_Franks"
in place of "Charles_Franks", but I still get the error message.

Any ideas how I can fix this mess up?

Thanks,
Charlie