Conference smurf::buildhelp

1754.0. "Defect number within my decx11-279-jing bsubmit" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Wed Aug 23 1995 16:44

Date Of Receipt: 	23-AUG-1995 12:35:45.07
From: 	SMURF::FLUME::"[email protected]"
To: 	flume::odehelp
CC: 	
Subj: 	Defect number within my decx11-279-jing bsubmit

Hi,

I sent a request regarding I mistakenly put the wrong defect numbers within my 
decx11-279-jing bsubmit last Friday.  I haven't received any responses yet.
Is there any way to fix it up manually?  

BTW, I checked /usr/sde/osf1/build/decx11.nightly/logs/bsubmit.log, but I couldn't
find out 10 files I've bsubmitted last week.  Do I have to do the bsubmit again?

Thanks for your help,
Jing


Return-Path: [email protected]
Received:  by locusla.wdec.locus.com (5.57/Ultrix3.0-C)
	id AA26967; Fri, 18 Aug 95 07:10:29 -0700
Received: from alpha.zk3.dec.com by decvax.dec.com (5.65/DEC-ULTRIX-8/19/92)
	id AA17784; Fri, 18 Aug 1995 10:05:34 -0400
Received: from localhost by alpha.zk3.dec.com; (5.65v3.0/1.1.8.2/20May95-1022AM)
	id AA07145; Fri, 18 Aug 1995 10:05:30 -0400
Message-Id: <[email protected]>
To: John Flanagan - UNIX Systems Group <[email protected]>, [email protected]
Cc: [email protected], [email protected]
Subject: Re: How did this defect number succeed? (DECX11 submits HPAQ6493D)
Date: Fri, 18 Aug 95 10:05:30 -0400
From: "Joshua M. Friedman, OSF/UNIX SDE 381-1548" <[email protected]>
X-Mts: smtp

I just looked at this again, and the submit was from 'alpha'; I checked
and alpha definitly has the submit wrapper in place, and the decx11 pool
is set to use it:

    longbow-520 % workon -sb decx11
    cd'ing to sandbox source directory: /usr/users/jmf/sb/decx11/src.
    starting new shell: /usr/ucb/csh.
    decx11-501 % sbinfo submit_defect
    true

So it would appear that Jing has either reset submit_defect to false in 
his environment (which is unfortunately possible) or is somehow calling
directly the "real" bsubmit (which is possible but unlikely).

Jing, can you explain?  Please do the srequest(s) if you haven't, and the
defect numbers can later be placed in the log.

Thanks...		-josh

------
Return-Path: johnf 
Delivery-Date: Fri, 18 Aug 95 08:47:41 -0400
Return-Path: johnf
Received: from localhost by flume.zk3.dec.com; (5.65v3.2/1.1.8.2/16Jan95-0946AM)
	id AA25839; Fri, 18 Aug 1995 08:47:38 -0400
Message-Id: <[email protected]>
X-Mailer: exmh version 1.6.2 7/18/95
To: jmf
Subject: How did this defect number succeed?
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 18 Aug 95 08:47:38 -0400
From: John Flanagan - UNIX Systems Group <johnf>
X-Mts: smtp


------- Forwarded Message

Return-Path: daemon
Received: from fsecret.zk3.dec.com by flume.zk3.dec.com; 
(5.65v3.2/1.1.8.2/16Jan95-0946AM)
	id AA03095; Thu, 17 Aug 1995 16:33:31 -0400
Received: by secret.zk3.dec.com; (5.65/1.1.8.2/19Aug94-1121AM)
	id AA26765; Thu, 17 Aug 1995 16:33:31 -0400
Date: Thu, 17 Aug 1995 16:33:31 -0400
From: system account <[email protected]>
Message-Id: <[email protected]>
To: [email protected], [email protected], [email protected]
Subject: DECX11 submits HPAQ6493D


Submission Log *****

  Submitted by Jing_Chang; User name: jing; Node name: alpha.zk3.dec.com
  Date: 8/17/95; Time: 16:18
  Coordinated Universal Time: 08/17/95 20:18:23 GMT
  Number of files: 1; Defect number: HPAQ6493D.
  Set name: Jing_Chang_decx11; Sandbox: /home/jing/sb/decx11
  List of files and revisions:
./motif/clients/mwm/WmGraphics.c,v	1.1.8.4

  Detailed description:

[ ./motif/clients/mwm/WmGraphics.c ]
Fix the following problem for #HPAQ6493D:
The text in an inactive ICON label is slightly off center and the
text in an active ICON label is truncated to the right.
[1995/08/17  20:17:52  Jing_Chang]

End Log *****


=================================================================
The following is the current hold log:


------- End of Forwarded Message




 ______________________________________________________________________

 John Flanagan	 		enet:    [email protected]	
 MS: ZKO3-3/W20			decnet:  flume::johnf
 USG Release Engineering		 (603) 881-1719
 110 Spitbrook Road 			 (DTN) 381-1719
 Nashua, NH  
 ______________________________________________________________________

Date Of Receipt: 	23-AUG-1995 13:01:20.19
From: 	SMURF::FLUME::johnf "John Flanagan USG Test Johnf Tools Group  23-Aug-1995 1259"
To: 	jing@dec:.zko.sysxt (Jing Chang LOCUS)
CC: 	odehelp@DEC:.zko.flume
Subj: 	Re: Defect number within my decx11-279-jing bsubmit

The wrong defect numbers aren't a problem.  In the future, however, please
enter the appropriate defect number given to you by srequest.


 ______________________________________________________________________

 John Flanagan	 		enet:    [email protected]	
 MS: ZKO3-3/W20			decnet:  flume::johnf
 USG Release Engineering		 (603) 881-1719
 110 Spitbrook Road 			 (DTN) 381-1719
 Nashua, NH  
 ______________________________________________________________________

Date Of Receipt: 	29-AUG-1995 16:38:12.18
From: 	SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE  29-Aug-1995 1636"
To: 	jing@dec:.zko.sysxt (Jing Chang LOCUS)
CC: 	flume::odehelp
Subj: 	Re: Defect number within my decx11-279-jing bsubmit

Jing,

Submits go into the "submit tree" - decx11 - this tree is built in 
an internal name-space and then, if the build is good, propagated to
decx11.nightly.  Only then will submits show up.  Hope this answers
your question.  As long as the files are in decx11/src and listed in
decx11/logs/bsubmit.log, they will eventually appear in .nightly.

-josh (just returning from vacation)

p.s. where did you do your submit from which had the qar/cld defect# ?
i.e. what 'hostname' were you on at the time?  The reason I ask is that
the system shouldn't have allowed it in.  If you did this locally at
locus, it may be we need to install our customization which may not
have been done at the time of the ode3.0 upgrade.