| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2678.1 | Re: Finding a file that was bcreated against another sandbox | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Mon Nov 18 1996 12:34 | 12 |
| Date Of Receipt: 18-NOV-1996 11:44:34.89
From: SEAN::davidson "D. Sean Davidson"
To: [email protected], [email protected]
CC:
Subj: Re: Finding a file that was bcreated against another sandbox
The ode blog command should give you some indication of where you created these
files. You will need to look in all your sandboxes for the matching setname
that the blog command shows you.
Sean
|
| 2678.2 | Re: Finding a file that was bcreated against another sandbox | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Mon Nov 18 1996 14:38 | 36 |
| Date Of Receipt: 18-NOV-1996 14:25:22.74
From: FLUME::jmf "Joshua M. Friedman Digital UNIX"
To: [email protected], [email protected], [email protected]
CC:
Subj: Re: Finding a file that was bcreated against another sandbox
Brian, a litt more info...
As Sean has said you can find your sandbox (well, set really) from the
blog output for the file. The best and safest thing to do is as Sean
recommends; workon to the sandbox where you did the bcreate, and outdate
there: bcs -u -o file.
If the correct sandbox has been deleted improperly, eg, with rm, then you
can access that sandbox's set using the -set switch of bcs (see the odeman
page). If you do this, and the other file still exists in another sandbox,
this can cause problems later, so it is always best to workon to the
original sandbox for the outdate.
-josh
> From [email protected] Mon Nov 18 11:41:29 1996
> Delivery-Date: Mon, 18 Nov 96 11:41:54 -0500
> Date: Mon, 18 Nov 1996 11:41:12 -0500
> From: D. Sean Davidson <[email protected]>
> To: [email protected], [email protected]
> Subject: Re: Finding a file that was bcreated against another sandbox
>
> The ode blog command should give you some indication of where you created these
> files. You will need to look in all your sandboxes for the matching setname
> that the blog command shows you.
>
> Sean
>
|
| 2678.3 | Re: Finding a file that was bcreated against another sandbox | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Mon Nov 18 1996 15:39 | 78 |
| Date Of Receipt: 18-NOV-1996 14:42:44.81
From: FLUME::masinick "Brian Masinick USG 18-Nov-1996 1439"
To: Joshua M. Friedman Digital UNIX <jmf@DEC:.zko.flume>
CC: [email protected], [email protected], [email protected],
masinick@DEC:.zko.flume
Subj: Re: Finding a file that was bcreated against another sandbox
This is all good information, but so far my attempts to locate this mythical
sandbox have been unsuccessful. Before 11AM this morning, I only had one
sandbox for the build pool steelcde.nightly. It was called mas_cde. Based on
some output that I gave to Sean, he noted that I had something called
qar44167. Now, I had intended to make that a set name, but perhaps I had
screwed up the command syntax and accidentally made a sandbox instead of a
set. Who knows?
What I'd really like to do at this point is get this junk defuncted out of the
"who knows where" place. If it is in RCS, it is bogus anyway because I had
made a typo in my first attempt. So far I've been spinning my wheels trying
to back out of it. It would sure help me out if someone would take a "cannon"
and blow these two files to oblivion. They only exist in my mythical sandbox
right now, and are not part of any inventory, so the risk to doing this is
zero.
files:
./doc/cde1/LearningProducts/fr_FR.ISO8859-1/DesktopIntro.hf
./doc/cde1/LearningProducts/de_DE.ISO8859-1/DesktopIntro.hf
sandbox: Sean thinks qar44167. I recreated one of those, recreated the
.BCSconfig and .BCSset files, still no luck.
pool: ???, but should be steelcde.nightly.
This is taking way too much time. I appeal to anyone who will listen to help
me get rid of the bad reference, preferably with a fast, high powered RCS
admin command.
Thanks in advance,
Brian
> Brian, a little more info...
>
> As Sean has said you can find your sandbox (well, set really) from the
> blog output for the file. The best and safest thing to do is as Sean
> recommends; workon to the sandbox where you did the bcreate, and outdate
> there: bcs -u -o file.
>
> If the correct sandbox has been deleted improperly, eg, with rm, then you
> can access that sandbox's set using the -set switch of bcs (see the odeman
> page). If you do this, and the other file still exists in another sandbox,
> this can cause problems later, so it is always best to workon to the
> original sandbox for the outdate.
>
> -josh
>
>
> > From [email protected] Mon Nov 18 11:41:29 1996
> > Delivery-Date: Mon, 18 Nov 96 11:41:54 -0500
> > Date: Mon, 18 Nov 1996 11:41:12 -0500
> > From: D. Sean Davidson <[email protected]>
> > To: [email protected], [email protected]
> > Subject: Re: Finding a file that was bcreated against another sandbox
> >
> > The ode blog command should give you some indication of where you created these
> > files. You will need to look in all your sandboxes for the matching setname
> > that the blog command shows you.
> >
> > Sean
> >
--
Brian W. Masinick WWW: http://www.zk3.dec.com/~masinick
Mailstop: ZKO3-3Y25 Internet mailto:[email protected]
110 Spit Brook Road FAX: (603) 881-2257
Nashua, NH 03062-2698 DTN: 381-0013; Phone: (603) 881-0013
Lower your monthly phone bill: http://www.freedomstarr.com/MA9668183.rep
|
| 2678.4 | Re: Finding a file that was bcreated against another sandbox | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Mon Nov 18 1996 16:43 | 34 |
| Date Of Receipt: 18-NOV-1996 15:59:58.52
From: SEAN::davidson "D. Sean Davidson"
To: sean::jmf, sean::masinick
CC: [email protected], [email protected], [email protected]
Subj: Re: Finding a file that was bcreated against another sandbox
We really don't like to stamp out RCS files because the only safe way to do
this is shutdown ode and we would get MANY complaints about that.
You should be able to create the sandbox with a (signle tab between ,v and 1.1)
in the .BCSconfig file.
Sean
% mksb -back steelcde -set qar44167 qar44167
% workon qar44167
% cat >.BCSconfig
./doc/cde1/LearningProducts/fr_FR.ISO8859-1/DesktopIntro.hf,v 1.1
./doc/cde1/LearningProducts/de_DE.ISO8859-1/DesktopIntro.hf,v 1.1
^D
% cat >.BCSset-Brian_Masinick_qar44167
./doc/cde1/LearningProducts/fr_FR.ISO8859-1/DesktopIntro.hf
./doc/cde1/LearningProducts/de_DE.ISO8859-1/DesktopIntro.hf
^D
% mkdir -p ./doc/cde1/LearningProducts/fr_FR.ISO8859-1
% touch ./doc/cde1/LearningProducts/fr_FR.ISO8859-1/DesktopIntro.hf
% mkdir -p ./doc/cde1/LearningProducts/de_DE.ISO8859-1
% touch ./doc/cde1/LearningProducts/de_DE.ISO8859-1/DesktopIntro.hf
%
% bcs -o -u ./doc/cde1/LearningProducts/fr_FR.ISO8859-1/DesktopIntro.hf
% bcs -o -u ./doc/cde1/LearningProducts/de_DE.ISO8859-1/DesktopIntro.hf
%
% mksb -undo qar44167
|
| 2678.5 | Re: Finding a file that was bcreated against another sandbox | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Mon Nov 18 1996 18:50 | 118 |
| Date Of Receipt: 18-NOV-1996 18:10:56.75
From: FLUME::jmf "Joshua M. Friedman Digital UNIX 18-Nov-1996 1807"
To: Brian Masinick <masinick@DEC:.zko.flume>
CC: [email protected]
Subj: Re: Finding a file that was bcreated against another sandbox
Brian, from any sandbox, backed by any cde pool, type:
bcs -u -o -set qar44167 \
/doc/cde1/LearningProducts/fr_FR.ISO8859-1/DesktopIntro.hf \
/doc/cde1/LearningProducts/de_DE.ISO8859-1/DesktopIntro.hf
This will "blow away" the RCS history.
Then start fresh by doing a "bco" and you'll get an empty file. You can
reset the comment leader if needed using
bcs -c"!# " file
and include /usr/sde/osf1/headers/header.hf at the top of the
file (I'm assuming this .hf format is the same as your's)
No need to make any bogus .BCS files.
FYI,
Somewhere you have a set, not a sandbox, called qar44167, and the file's
listed in a .BCSset-Brian_Masinick_qar44167 file, however you can ignore
this; just beware that it could bite you if you try to use a new version
of this file sometime in the future in that sandbox or set.
-josh
----------
To: Joshua M. Friedman Digital UNIX <jmf>
Cc: [email protected], [email protected], [email protected],
masinick
Subject: Re: Finding a file that was bcreated against another sandbox
In-Reply-To: Your message of "Mon, 18 Nov 96 14:21:45 EST."
<[email protected]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 18 Nov 96 14:39:17 -0500
From: Brian Masinick <masinick>
X-Mts: smtp
Status: RO
This is all good information, but so far my attempts to locate this mythical
sandbox have been unsuccessful. Before 11AM this morning, I only had one
sandbox for the build pool steelcde.nightly. It was called mas_cde. Based on
some output that I gave to Sean, he noted that I had something called
qar44167. Now, I had intended to make that a set name, but perhaps I had
screwed up the command syntax and accidentally made a sandbox instead of a
set. Who knows?
What I'd really like to do at this point is get this junk defuncted out of the
"who knows where" place. If it is in RCS, it is bogus anyway because I had
made a typo in my first attempt. So far I've been spinning my wheels trying
to back out of it. It would sure help me out if someone would take a "cannon"
and blow these two files to oblivion. They only exist in my mythical sandbox
right now, and are not part of any inventory, so the risk to doing this is
zero.
files:
./doc/cde1/LearningProducts/fr_FR.ISO8859-1/DesktopIntro.hf
./doc/cde1/LearningProducts/de_DE.ISO8859-1/DesktopIntro.hf
sandbox: Sean thinks qar44167. I recreated one of those, recreated the
.BCSconfig and .BCSset files, still no luck.
pool: ???, but should be steelcde.nightly.
This is taking way too much time. I appeal to anyone who will listen to help
me get rid of the bad reference, preferably with a fast, high powered RCS
admin command.
Thanks in advance,
Brian
> Brian, a little more info...
>
> As Sean has said you can find your sandbox (well, set really) from the
> blog output for the file. The best and safest thing to do is as Sean
> recommends; workon to the sandbox where you did the bcreate, and outdate
> there: bcs -u -o file.
>
> If the correct sandbox has been deleted improperly, eg, with rm, then you
> can access that sandbox's set using the -set switch of bcs (see the odeman
> page). If you do this, and the other file still exists in another sandbox,
> this can cause problems later, so it is always best to workon to the
> original sandbox for the outdate.
>
> -josh
>
>
> > From [email protected] Mon Nov 18 11:41:29 1996
> > Delivery-Date: Mon, 18 Nov 96 11:41:54 -0500
> > Date: Mon, 18 Nov 1996 11:41:12 -0500
> > From: D. Sean Davidson <[email protected]>
> > To: [email protected], [email protected]
> > Subject: Re: Finding a file that was bcreated against another sandbox
> >
> > The ode blog command should give you some indication of where you created these
> > files. You will need to look in all your sandboxes for the matching setname
> > that the blog command shows you.
> >
> > Sean
> >
--
Brian W. Masinick WWW: http://www.zk3.dec.com/~masinick
Mailstop: ZKO3-3Y25 Internet mailto:[email protected]
110 Spit Brook Road FAX: (603) 881-2257
Nashua, NH 03062-2698 DTN: 381-0013; Phone: (603) 881-0013
Lower your monthly phone bill: http://www.freedomstarr.com/MA9668183.rep
|