Conference smurf::buildhelp

Date Of Receipt: 	24-JAN-1994 09:21:27.34
From: 	QUARRY::aju "Aju John USG/BaseOS  24-Jan-1994 0921"
To: 	Joshua M. Friedman ULTRIX SDE <jmf@DEC:.zko.quarry>
CC: 	odehelp@DEC:.zko.quarry, cascio@DEC:.zko.quarry
Subj: 	Re: bsubmit problems - stat errors

Hi Josh,

There doesn't seem to be any netowrk or filesystem related problem.
In fact, ODE commands such as bco and bci works just fine.

As you suggested, I did a bco -u -all and then retried bsubmit -resub.

This time, the errors were different:


>> FATAL ERROR in /usr/sde/ode2.0/tools/alpha_ace/bin/ode/bsubmit:
>> Discrepancy between bcs tracking file and hold file.
>> A file listed in the bcs tracking file was not present in the hold file.
>> File: './kernel/cdfs/cdfs_lookup.c'

Please take appropriate steps and re-submit.

*** RE-SUBMISSION REQUIRED ***

- Source control information is in an intermediate state.
- Re-submit using -resub 17:54 [ -date 1/21/94 ]

I checked the lock files and the BCSset. There are duplicate
entries in them. I don't know how these files work, but I can't
tell why there should be duplicate entries, either.


Thanks,
-aju

Date Of Receipt: 	24-JAN-1994 09:43:30.70
From: 	QUARRY::aju "Aju John USG/BaseOS  24-Jan-1994 0943"
To: 	jmf@DEC:.zko.quarry
CC: 	odehelp@DEC:.zko.quarry, cascio@DEC:.zko.quarry
Subj: 	Re:  bsubmit problems - stat errors

Josh,

I tried resubmiting after deleting all duplicate entries from 
the files: .BCSset-Aju_John_goldos  and 17:54.Thold.

Unfortunately, it resulted in more errors:

proton:/usr/sb1/goldos/src$ bsubmit -resub 17:54 -date 1/21/94
Enter the defect number this submission applies to: goldos-1142-aju

ci error: no lock set by Aju_John for revision 4.2.19.7
[ ./kernel/ufs/ufs_lookup.c checked in onto branch 4.2.19 ]
ci error: no lock set by Aju_John for revision 1.1.2.11
[ ./kernel/nfs/nfs3_vnodeops.c checked in onto branch 1.1.2 ]
ci error: no lock set by Aju_John for revision 1.1.31.16
[ ./kernel/nfs/nfs_vnodeops.c checked in onto branch 1.1.31 ]
ci error: no lock set by Aju_John for revision 4.3.18.6
[ ./kernel/cdfs/cdfs_lookup.c checked in onto branch 4.3.18 ]
ci error: no lock set by Aju_John for revision 4.3.11.9
[ ./kernel/sys/param.h checked in onto branch 4.3.11 ]
ci error: no lock set by Aju_John for revision 4.3.24.19
[ ./kernel/conf/param.c checked in onto branch 4.3.24 ]
ci error: no lock set by Aju_John for revision 4.4.28.9
[ ./kernel/src/config/mkmakefile.c checked in onto branch 4.4.28 ]
ci error: no lock set by Aju_John for revision 4.3.21.7
[ ./kernel/src/config/config.h checked in onto branch 4.3.21 ]
ci error: no lock set by Aju_John for revision 4.2.17.5
[ ./kernel/src/config/config.l checked in onto branch 4.2.17 ]
ci error: no lock set by Aju_John for revision 4.4.20.5
[ ./kernel/src/config/config.y checked in onto branch 4.4.20 ]
ci error: no lock set by Aju_John for revision 1.1.8.6
[ ./kernel/conf/alpha/ADU checked in onto branch 1.1.8 ]
ci error: no lock set by Aju_John for revision 1.2.60.30
[ ./kernel/conf/alpha/BINARY checked in onto branch 1.2.60 ]
ci error: no lock set by Aju_John for revision 1.1.4.30
[ ./kernel/conf/alpha/BINARY.ext checked in onto branch 1.1.4 ]
ci error: no lock set by Aju_John for revision 1.1.28.24
[ ./kernel/conf/alpha/COBRA checked in onto branch 1.1.28 ]
ci error: no lock set by Aju_John for revision 1.1.4.22
[ ./kernel/conf/alpha/COBRA.ext checked in onto branch 1.1.4 ]
ci error: no lock set by Aju_John for revision 1.1.31.21
[ ./kernel/conf/alpha/FLAMINGO checked in onto branch 1.1.31 ]
ci error: no lock set by Aju_John for revision 1.1.4.24
[ ./kernel/conf/alpha/FLAMINGO.ext checked in onto branch 1.1.4 ]
ci error: no lock set by Aju_John for revision 1.2.39.24
[ ./kernel/conf/alpha/GENERIC checked in onto branch 1.2.39 ]
ci error: no lock set by Aju_John for revision 1.1.4.26
[ ./kernel/conf/alpha/GENERIC.ext checked in onto branch 1.1.4 ]
ci error: no lock set by Aju_John for revision 1.1.14.13
[ ./kernel/conf/alpha/JENSEN checked in onto branch 1.1.14 ]
ci error: no lock set by Aju_John for revision 1.1.2.15
[ ./kernel/conf/alpha/JENSEN.ext checked in onto branch 1.1.2 ]
ci error: no lock set by Aju_John for revision 1.1.8.12
[ ./kernel/conf/alpha/PELICAN checked in onto branch 1.1.8 ]
ci error: no lock set by Aju_John for revision 1.1.2.13
[ ./kernel/conf/alpha/PELICAN.ext checked in onto branch 1.1.2 ]
ci error: no lock set by Aju_John for revision 1.1.25.25
[ ./kernel/conf/alpha/RUBY checked in onto branch 1.1.25 ]
ci error: no lock set by Aju_John for revision 1.1.4.22
[ ./kernel/conf/alpha/RUBY.ext checked in onto branch 1.1.4 ]
ci error: no lock set by Aju_John for revision 1.2.37.26
[ ./kernel/conf/alpha/SAS checked in onto branch 1.2.37 ]

Please take appropriate steps and re-submit.

*** RE-SUBMISSION REQUIRED ***

- Source control information is in an intermediate state.
- Re-submit using -resub 17:54 [ -date 1/21/94 ]



FYI

-aju

Date Of Receipt: 	24-JAN-1994 10:35:12.97
From: 	QUARRY::aju "Aju John USG/BaseOS  24-Jan-1994 1035"
To: 	Joshua M. Friedman ULTRIX SDE <jmf@DEC:.zko.quarry>
CC: 	odehelp@DEC:.zko.quarry, cascio@DEC:.zko.quarry, stuarth@DEC:.zko.quarry,
	aju@DEC:.zko.quarry
Subj: 	Re: bsubmit problems - stat errors

Josh,

Making all the entries in the hidden files unique and resorting them
helped! Bsubmit succeeded.

Thanks much for you assistance.

-aju

---------------------------------------------------------
proton:/usr/sb1/goldos/src$ bsubmit -resub 17:54 -date 1/21/94
Enter the defect number this submission applies to: goldos-1142-aju

[ ./kernel/cdfs/cdfs_lookup.c Rev 4.3.18.6 checked out ]
[ ./kernel/conf/alpha/ADU Rev 1.1.8.6 checked out ]
[ ./kernel/conf/alpha/BINARY Rev 1.2.60.30 checked out ]
[ ./kernel/conf/alpha/BINARY.ext Rev 1.1.4.30 checked out ]
[ ./kernel/conf/alpha/COBRA Rev 1.1.28.24 checked out ]
[ ./kernel/conf/alpha/COBRA.ext Rev 1.1.4.22 checked out ]
[ ./kernel/conf/alpha/FLAMINGO Rev 1.1.31.21 checked out ]
[ ./kernel/conf/alpha/FLAMINGO.ext Rev 1.1.4.24 checked out ]
[ ./kernel/conf/alpha/GENERIC Rev 1.2.39.24 checked out ]
[ ./kernel/conf/alpha/GENERIC.ext Rev 1.1.4.26 checked out ]
[ ./kernel/conf/alpha/JENSEN Rev 1.1.14.13 checked out ]
[ ./kernel/conf/alpha/JENSEN.ext Rev 1.1.2.15 checked out ]
[ ./kernel/conf/alpha/PELICAN Rev 1.1.8.12 checked out ]
[ ./kernel/conf/alpha/PELICAN.ext Rev 1.1.2.13 checked out ]
[ ./kernel/conf/alpha/RUBY Rev 1.1.25.25 checked out ]
[ ./kernel/conf/alpha/RUBY.ext Rev 1.1.4.22 checked out ]
[ ./kernel/conf/alpha/SAS Rev 1.2.37.26 checked out ]
[ ./kernel/conf/param.c Rev 4.3.24.19 checked out ]
[ ./kernel/kern/lockinfo.c Rev 1.1.2.66 checked out ]
[ ./kernel/msfs/osf/msfs_lookup.c Rev 1.1.3.5 checked out ]
[ ./kernel/nfs/nfs3_vnodeops.c Rev 1.1.2.11 checked out ]
[ ./kernel/nfs/nfs_vnodeops.c Rev 1.1.31.16 checked out ]
[ ./kernel/src/config/config.h Rev 4.3.21.7 checked out ]
[ ./kernel/src/config/config.l Rev 4.2.17.5 checked out ]
[ ./kernel/src/config/config.y Rev 4.4.20.5 checked out ]
[ ./kernel/src/config/mkmakefile.c Rev 4.4.28.9 checked out ]
[ ./kernel/sys/param.h Rev 4.3.11.9 checked out ]
[ ./kernel/sys/vnode.h Rev 4.3.23.14 checked out ]
[ ./kernel/ufs/ufs_lookup.c Rev 4.2.19.7 checked out ]
[ ./kernel/vfs/vfs_cache.c Rev 4.2.7.4 checked out ]
[ ./kernel/vfs/vfs_subr.c Rev 4.3.17.16 checked out ]

*** Please mail the log, /usr/sb1/goldos/src/17:54.Tlog,
*** to the appropriate people in your project then remove.

Outdate the submitted files from set Aju_John_goldos?
Outdate files?: [Yes] yes

Date Of Receipt: 	24-JAN-1994 10:38:45.04
From: 	WASTED::jmf "Joshua M. Friedman ULTRIX SDE"
To: 	aju@wasted:zko.dec
CC: 	cascio odehelp stuarth
Subj: 	Re: bsubmit problems - stat errors

you're welcome ... unfortunately it's a mystery as to how the duplicates
got in the .BCSset-* file in the first place....

-josh

Date Of Receipt: 	 7-MAR-1995 17:53:52.41
From: 	SMURF::WASTED::"[email protected]" "07-Mar-1995 1751"
To: 	[email protected]
CC: 	
Subj: 	bsubmit problems

I have just completed a project and when I invoked "bsubmit -all" received
a large number of errors of the form:

*** No user interaction will be required during the merge step. ***


*** VALIDATION FAILURE ***

path/to/file -- not checked in. locked.
path/to/file -- not checked in. locked.

Consult the bsubmit reference page for suggested corrective actions.

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.


Now I do not know how to continue.  I was able to reproduce the problem by
bcs -o -u * and then bco/bci/bsubmit'ing.


Can you shed some light as to what is happening?


Martin Buckley

Date Of Receipt: 	 7-MAR-1995 18:38:07.63
From: 	SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE"
To: 	[email protected], [email protected]
CC: 	
Subj: 	Re:  bsubmit problems

If you're sure that the bci's were completed, i.e. the files were all
read-only and blog confirmed that there were no private branch locks
before beginning the submit, then this sounds like a more "involved"
problem which DECwest decwet::ode ought to help with (they are cc'd
on odehelp).  Be sure that the bco and bci and bsubmit were all done
from within the same sandbox and set.

-josh

	From [email protected]  Tue Mar  7 17:53:08 1995
	Delivery-Date: Tue, 07 Mar 95 17:53:14 -0500
	Return-Path: [email protected]
	Received: from abelia.zk3.dec.com by flume.zk3.dec.com; (5.65/1.1.8.2/16Jan95-0946AM)
		id AA04961; Tue, 7 Mar 1995 17:53:08 -0500
	Received: from avalon.Eng.PKO.DEC.Com by wasted.zk3.dec.com; (5.65 EXP 2/22/95 for V3.2/1.1.8.2/18Feb95-1123AM)
		id AA07917; Tue, 7 Mar 1995 17:52:39 -0500
	Received: from localhost by avalon.eng.pko.dec.com; (5.65/1.1.7.2/22Nov94-1009PM)
		id AA08335; Tue, 7 Mar 1995 17:51:53 -0500
	Message-Id: <[email protected]>
	To: [email protected]
	Subject: bsubmit problems
	Date: Tue, 07 Mar 95 17:51:53 -0500
	From: [email protected]
	X-Mts: smtp
	
	
	I have just completed a project and when I invoked "bsubmit -all" received
	a large number of errors of the form:
	
	*** No user interaction will be required during the merge step. ***
	
	
	*** VALIDATION FAILURE ***
	
	path/to/file -- not checked in. locked.
	path/to/file -- not checked in. locked.
	
	Consult the bsubmit reference page for suggested corrective actions.
	
	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.
	
	
	Now I do not know how to continue.  I was able to reproduce the problem by
	bcs -o -u * and then bco/bci/bsubmit'ing.
	
	
	Can you shed some light as to what is happening?
	
	
	Martin Buckley
	

Date Of Receipt: 	 7-MAR-1995 19:02:23.73
From: 	SMURF::WASTED::"[email protected]" "07-Mar-1995 1900"
To: 	Joshua M. Friedman OSF/UNIX SDE <[email protected]>
CC: 	[email protected]
Subj: 	Re: bsubmit problems

I got around this problem, finally.  Not exactly sure what caused it though.
Reboot of our ode machine seemed to clear up the problem.  I had to 
bcs -o -u all files and restart changes to get it to work.

An unsolved mistery...

Martin

Date Of Receipt: 	21-MAY-1996 11:48:41.79
From: 	WASTED::dewandel "Mark Dewandel USG"
To: 	[email protected]
CC: 	
Subj: 	bsubmit problems

I am having no success in issuing bsubmit from my workstation.
Running from my sandbox, the following behavior is manifested:

ode.proto:kernel> bsubmit -all
Enter the defect number this submission applies to: steelos-331-dewandel

/usr/sde/osf1/bin/alpha_OSF1/bsubmit[227]: /usr/sde/osf1/bin/alpha_OSF1/ode/bsubmit:  not found

Do you have any suggestions?

Thanks,

Mark

-- 
Mark S. DeWandel                         [email protected]
Digital Equipment Corporation            Voice:  603-881-1434
110 Spit Brook Road, ZK03-3/U14          FAX:    603-881-2257
Nashua, NH 03062-2698                    DTN:    381-1434

Date Of Receipt: 	21-MAY-1996 12:05:21.70
From: 	FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE"
To: 	dewandel@DEC:.zko.flume
CC: 	odehelp@DEC:.zko.flume
Subj: 	Re:  bsubmit problems

Can you check that you're in group staff (groups)?

Check that this file exists:

ls -l /usr/sde/osf1/bin/alpha_OSF1/ode/bsubmit

What is your /usr/sde server?  (df /usr/sde/)

-josh

Date Of Receipt: 	21-MAY-1996 14:19:24.15
From: 	FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE  21-May-1996 1412"
To: 	dewandel@DEC:.zko.flume
CC: 	odehelp@DEC:.zko.flume
Subj: 	re: bsubmit problems

Mark, I think I found the problem.  The "correct" path for the /usr/sde
bsubmit tool is

	/usr/sde/tools/alpha_OSF1/bin/bsubmit
	(this is a link to /usr/sde/osf1/bin/alpha_OSF1/bsubmit)
	which in turn calls /usr/sde/tools/alpha_OSF1/bin/ode/bsubmit

Somehow your system is calling /usr/sde/osf1/bin/alpha_OSF1/bsubmit
from that path directly, rather than from /usr/sde/tools/....  This is
then looking for /usr/sde/osf1/bin/alpha_OSF1/ode/bsubmit which doesn't
and shouldn't exist.

I suspect that you have /usr/sde/osf1/bin/alpha_OSF1 in your PATH. You
should either not have this in your path, or, if you need it for some
reason, it should appear after the normal ode path of:
/usr/sde/tools/alpha_OSF1/bin .  This path can be specified within your
PATH definition as /usr/sde/tools/`machine`_`uname`/bin or
`/usr/sde/tools/common/ode_uname -p`, to keep it generic.

-josh




------- Forwarded Message

From: Mark Dewandel USG <dewandel>
Subject: bsubmit problems
To: [email protected]
Date: Tue, 21 May 1996 11:42:13 -0500 (EDT)

I am having no success in issuing bsubmit from my workstation.
Running from my sandbox, the following behavior is manifested:

ode.proto:kernel> bsubmit -all
Enter the defect number this submission applies to: steelos-331-dewandel

/usr/sde/osf1/bin/alpha_OSF1/bsubmit[227]: /usr/sde/osf1/bin/alpha_OSF1/ode/bsubmit:  not found

Do you have any suggestions?

Thanks,

Mark

- -- 
Mark S. DeWandel                         [email protected]
Digital Equipment Corporation            Voice:  603-881-1434
110 Spit Brook Road, ZK03-3/U14          FAX:    603-881-2257
Nashua, NH 03062-2698                    DTN:    381-1434


------- End of Forwarded Message