| Date Of Receipt: 27-SEP-1994 12:03:51.70
From: ABYSS::schulter "Peter Schulter USEG 27-Sep-1994 1201"
To: ode@dec:.zso.rust (ode)
CC: [email protected]
Subj: Re: bsubmit confused about set contents - HELP!
That worked.
Thanks,
--- pete
----------------------------------------------------
hi peter,
the suspect at this time is the set name of atmproj_Peter_Schulter_bl6
a normal set name is principal_name_setname e.g. Peter_Schulter_bl6.
i'm still investigating the source but to get your submit going,
try
bsubmit -set atmproj_Peter_Schulter_bl6
let me know if this gets your submit in.
jo
|
| Date Of Receipt: 27-SEP-1994 12:35:28.80
From: ABYSS::"[email protected]" "27-Sep-1994 0932"
To: Peter "If the software don't work, rewire the hardware" Schulter <[email protected]>
CC: [email protected], [email protected], flambe::jmf
Subj: Re: bsubmit confused about set contents - HELP!
peter,
good to hear that bsubmit -set worked for you.
this is a bug that we will look into. i'll file a ptt with the info you've sent
out. this situation arises when a sandbox is created under a principal name and
files checked-out under a different principal name. or something like that.
that's as close as we got to reproducing the problem.
to avoid this in the future, be very careful when using 2 different principal
names. a branch name other than principal_name_setname e.g. Peter_Schulter_bl6
is suspect. bco and bci works but bsubmit trips over malformed set names
like atmproj_Peter_Schulter_bl6. but for now, you know what the work around is.
jo
|