Subject: Re: 2.5m obslog 20030220 (MJD 52691)
Date: Tue, 25 Feb 2003 10:43:56 -0700 (MST)
From: sjnk@apo.nmsu.edu (Scot Kleinman)
Dan wrote:
>There appears to be an odd dependency problem with iop v3_109_2 compared to
>v3_109_1.  When mcpMenu is run under v3_109_2, the PLC version is ???.  Under
>v3_109_1 is shows properly that PLC is v14.  The curious thing is that a ups
>depend of each of the iops is identical and shows the plc version to be v14.
>Since the mcp knows what version of the plc is running, and apparently so does
>iop, is the mcpMenu not displaying the plc version simply a cosmetic problem
>or is there a more significant issue behind it?
  Hmm, this is a bit strange. We had a problem with this in v3_109_0, which
Robert fixed in version v_3_109_1. If v3_109_2 really is another leaf on
the v3_109 branch, this misfeature should not have re-appeared.  Is it
still the case?  Checking the dependency tree was indeed the right thing to
do here, but I do not believe the mcpMenu gets the PLC version from this
dependency.  Sure enough, if you type (in IOP):
im> plcVersion
you get an error.  Indeed, there's a difference in the plcVersion command
between v3_109_1 and v3_109_2 which is causing the problem:
Host%diff /p/iop/v3_109_1/etc/mcp.tcl /p/iop/v3_109_2/etc/mcp.tcl
371c371
    if {![regexp {Version ([^ ]+) [$]Name: ([^ ]+)} \
If you remove the extra + in the v3_109_2 version (how did it get there?),
the mismatch problem will go away. I suggest you talk to Eric and/or Robert
about cutting a new branch version with this change. It is harmless in this
instance, but it's very bad practice to encourage people to ignore an
mcpMenu-reported PLC mismatch or ???.
>Something else ups depend shows is that both versions depend on v2_24_0 of the
>tpm when the latest is v2_26_0.  Shouldn't iop with the new plc code depend on
>the latest version of the tpm?
Yes, I noticed that, too. For some reason, the ups.table file for IOP
setsup the CURRENT version of the TPM in its dependency no matter what
version you manually setup during the build (otherwise, you just setup the
new version of TPM before you build your test version of IOP).  I don't
know why this is and suspect it's something we should fix. Peregrine, Eric?
Scot