[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference smurf::buildhelp

Title:USG buildhelp questions/answers
Moderator:SMURF::FILTER
Created:Mon Apr 26 1993
Last Modified:Mon Jan 20 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2763
Total number of notes:5802

765.0. "how does one get copies of defunct files?" by SMURF::FILTER (Automatic Posting Software - mail to flume::puck) Fri Jun 03 1994 12:29

Date Of Receipt: 	27-MAY-1994 16:42:00.68
From: 	MINSRV::ftw "Farrell Woods USG  27-May-1994 1639"
To: 	odehelp@DEC:.zko.minsrv
CC: 	
Subj: 	how does one get copies of defunct files?

I want to look at the sources for a defunct scsi driver.  I know where
it lives, but bco refuses to let me see a copy because the file
is defunct.  How to I get around this?

Thanks,


	-- Farrell
T.RTitleUserPersonal
Name		DateLines
765.1Re: how does one get copies of defunct files?SMURF::FILTERAutomatic Posting Software - mail to flume::puckFri Jun 03 1994 12:4018
Date Of Receipt: 	27-MAY-1994 16:59:52.44
From: 	MINSRV::"[email protected]"
To: 	[email protected], [email protected]
CC: 	
Subj: 	Re:  how does one get copies of defunct files?

Farrell, whenever a submit is done to defunct a file, a new version
is created, and that version's marked defunct.  If you find the
file you want, do a blog -r file  or blog -rGOLDOS file (for example)
to see all the history along that branch.  Get the rev just BEFORE
the version marked defunct, and check that out.

e.g. suppose the defunct rev is 1.1.5.17, do:

	bco -u -r1.1.5.16 filename

-josh
765.2Re: how does one get copies of defunct files?SMURF::FILTERAutomatic Posting Software - mail to flume::puckFri Jun 03 1994 12:4220
Date Of Receipt: 	27-MAY-1994 17:16:04.18
From: 	MINSRV::ftw "Farrell Woods USG  27-May-1994 1715"
To: 	Joshua M. Friedman OSF/UNIX SDE <[email protected]>
CC: 	[email protected]
Subj: 	Re: how does one get copies of defunct files?

> 	bco -u -r1.1.5.16 filename

I had braced myself for something much more convoluted than this!  Thanks
Josh.  On a related note: suppose there are several files made defunct
in the same directory.  But I don't know their names.  A "bsh ls" won't
reveal them because they're defunct, and I can't "blog" and subsequently
"bco" a file without knowing its name.  How would I get the names of
those defuncted files?


Thanks again,

	-- Farrell
765.3defunct filesAOSG::FILTERAutomatic Posting Software - mail to flume::puckWed Nov 29 1995 19:0224
Date Of Receipt: 	29-NOV-1995 18:08:11.86
From: 	SMURF::TLAZA::winchell "David Winchell  29-Nov-1995 1806"
To: 	odehelp@DEC:.zko.tlaza
CC: 	winchell@DEC:.zko.tlaza
Subj: 	defunct files

When I try to bco pmap.c in a sanbox backed by the clutwav3os tree
I get the following:

jibe.zk3.dec.com[865] bco pmap.c

[ ./kernel/arch/alpha/pmap.c ]
bco: no checkout allowed: ./kernel/arch/alpha/pmap.c is defunct




How can I get past this?  The file should not be marked defunct.


thanks,
dave
765.4Re: defunct filesAOSG::FILTERAutomatic Posting Software - mail to flume::puckWed Nov 29 1995 19:0330
Date Of Receipt: 	29-NOV-1995 18:25:25.63
From: 	SMURF::ALPHA::"[email protected]" "29-Nov-1995 1523"
To: 	[email protected]
CC: 	[email protected]
Subj: 	Re: defunct files

   If you accidently defuncted this file by mistake,
   in your own sandbox and on your private branch or setname,
  just outdate your branch of the file with:
  
   bcs -o <file>

   If the file is defunct in the submit tree, and you
   are positive that this is the file you want
   to apply some changes to, you must undefunct it first,
   i.e. change the state of the defunct file's revision, from
   "defunct" to "Exp", and  have it available to check_out, with bco.

   from a sandbox back to the submit tree where the file'revision
   is defunct :

   undefunct <file>
   bco <file> 
   aply your changes ...
   bci ...
   bsubmit ... 


/Rima