Solaris x86 10 u1 (01/06) Update manager showing obsolete patches

I installed 10 u1 (01/06) the other day. I ran the Update Manager and I *think* there were 8 patches, so I attempted to install them.

Only one of them successfully installed (118966-12), six of them show up in /var/sadm/spool/disallwed_patch_list_report:

STATUS INSTALL BEGIN 119076-10

Transition old-style patching.

STATUS INSTALL END 119076-10 INSTALL.6

STATUS INSTALL BEGIN 119833-02

Transition old-style patching.

STATUS INSTALL END 119833-02 INSTALL.6

STATUS INSTALL BEGIN 120470-02

Transition old-style patching.

STATUS INSTALL END 120470-02 INSTALL.6

STATUS INSTALL BEGIN 120082-07

Transition old-style patching.

STATUS INSTALL END 120082-07 INSTALL.6

STATUS INSTALL BEGIN 120666-01

Transition old-style patching.

STATUS INSTALL END 120666-01 INSTALL.6

STATUS INSTALL BEGIN 119684-02

Transition old-style patching.

STATUS INSTALL END 119684-02 INSTALL.6

And the last one (120041-02) failed.

Anyway, I was grep'ing patchadd -p for some of these and it looks like the ones I checked have been obsoleted by other patches (I didn't check them all, maybe 3).

So, why do they still show up in Update Manager? Or am I missing something (very possible, I'm not a sysadmin, I use this machine for development).

[1350 byte] By [scottie_mac_325] at [2007-11-26 6:05:02]
# 1

I have just installed S10 1/06 and only 1 out of 20 patches installed successfully. I have 19 patches showing up as available to install in update manager or through http://updates.sun.com/ and when I t ry to install them I get "A newer patch revision is already installed" but they keep showing up. I think from the start these patches should not be displayed. Apparently the analysis algorithm applied by updatemanager to my system doesn`t take into account all the rules that govern patching, like conflicts, revision numbers and obsolescence by a different patch. Can we get any help from Sun?

datique at 2007-7-6 13:31:50 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 2

The same problem:

smpatch analyze

119076-10 SunOS 5.10_x86: ip Patch

119833-02 SunOS 5.10_x86: gld patch

120082-07 SunOS 5.10_x86: bge patch

120666-01 SunOS 5.10_x86: busra patch

119684-02 SunOS 5.10_x86: lib/svc/bin/svc.configd Patch

120470-02 SunOS 5.10_x86: kerberos patch

120041-02 SunOS 5.10_x86: ata patch

patchadd -p | egrep "119076|119833|120082|120666|119684|120470|120041"

Patch: 118844-26 Obsoletes: 117462-04 118549-01 118552-03 118847-01 118851-02 118860-01 118993-03 119206-01 119208-01 119565-01 119830-01 119859-02 120320-01 118863-01 119590-03 119720-01 118922-07 119076-12 119946-03 119952-01 120014-02 120029-02 120132-01 120363-01 118924-03 119684-02 119833-02 119948-02 119950-02 119991-01 119995-01 120067-01 120082-07 120303-01 120470-02 120666-01 119857-01 120041-02 118886-01 Requires: 113000-01 118344-05 119255-08 Incompatibles: Packages: ...

Now look to file "patchlist.delimited" from /var/sadm/spool/cache/Database/*.zip (this file is downloaded automaticaly and used for analysis) for patch 118844:

118844<!>20<!>SunOS 5.10_x86: kernel Patch<!>i386<!>SunOS<!>5.10<!>118344-05 <!>118851-02 118860-01 118993-03 119206-01 119208-01 119565-01 119830-01 119859-02 120320-01 118863-01 119590-03 119720-01 <!><!><!><!>BaseOS.SolarisSunIEEE1394-5.10 .... <!><!>reconfigimmediate singleuser clientroot clientusr noncontract<!><!>9361303<!>20051028<!><!>

AND:

there is recorded only 118844-20 and NOT 118844-26 in the "central update" database, therefore obsolete patch path is not resolved correctly (look at 8 field).

SOLUTION:

We must wait :-)

M.C>

mcerveny at 2007-7-6 13:31:50 > top of Java-index,Administration Tools,Sun Update Connection-System...