Sun Update Connection Bootstrapper patch install fails on my S10 system
I just tried to install this patch along with the Sun Update Connection System Client 1.0.8 patch and I see in the Installation Complete window this:
122761-01
SunOS 5.10: Sun Update Connection Bootstrapper
Failed
Utility used to install the update failed with exit code {0}.
This occurred using Update Manager 1.0.4a on a S10 system with various patches.
# 2
The older boxes are missing packages SUNWswupcl, SUNWswupclr
which this patch patches.
Those packages are on the S10u2 image, so I would expect they can just be manually installed.
However, its not immediately obvious to me that they do anything useful.
They contained a startup script at one stage, but it looks like its been dropped from the startup sequence.
So I don't know if its a problem to leave it unpatched (and uninstalled).
Except that it hangs around in the list of patches to be installed.
In theory, it shouldnt be offering patches for packages that arent installed.
So I guess this represents a bug.
I guess I'll wait for a response from the moderator as to whether (and when) their likely to address this.
But failing a speedy resolution the simplest fix is to just install the packages manually and then the patch should go in cleanly.
# 3
The trick here is that smpatch uses "realizations" to determine what is applicable. It appearst that for this patch the realizations are too broad. Essentially this is smpatch doing the right thing on metadata which needs refinement to be more targetted.Once the metadata is fixed, the patch should no longer show up as recommended on systems where the required packages aren't installed.
Summary:
The metadata for that patch thinks it is more generally applicable than it really is. Future, more accurate, metadata about the patch should fix this.
# 5
This patch should only be applicable to systems where those two packages, SUNWswupcl and SUNWswupclr, are installed. This appears to be only for Solaris 10 Update 1 1/06 and Update 2 6/06 as they are not present with 3/05 and should be removed for Update 3.
I will raise a request to have the metadata updated so the patch is no longer recommended on system where it is unnecessary.