Hi Enda,

> There is also a seperate miniroot issues in that the KU cannot be 
> applied because the prepatch now checks if we ran a patchadd -C  and
> if so, then proceeds to test if a package SUNWicda which is only
> specific to update 3 is in the miniroot.

SUNWicda is part of the mini-root on all the Solaris 10 releases
including GA. From my local network install image for GA:

                          Solaris 10 3/05 s10_74L2a SPARC
            Copyright 2005 Sun Microsystems, Inc.  All Rights Reserved.
                         Use is subject to license terms.
                             Assembled 22 January 2005

    PKGINST:  SUNWicda
       NAME:  Installer CD System administration applications
   CATEGORY:  system
       ARCH:  sparc
    VERSION:  11.10,REV=2005.01.09.23.05
    BASEDIR:  /
     VENDOR:  Sun Microsystems, Inc.
       DESC:  Installer CD Software used to perform system administration
tasks
     PSTAMP:  install-bldsp-1020050109230552
   INSTDATE:  Jan 22 2005 19:16
    HOTLINE:  Please contact your local service provider
     STATUS:  spooled

> We need to either

> 1 rip this dependency on SUNWicda out somehow ( not clear what is in
> the KU that now requires the miniroot have an update 3 onwards
> package SUNWicda )

See my separate email and the update I made to:

   6481557 patch T118833-29 will not install in miniroot
   <http://monaco.sfbay/detail.jsf?cr=6481557>

> 2 if we cannto rip it out we need to investigate if we can somehow
> via genesis add SUNWicda to the miniroot Not clear what effect this
> will have on FCS,U1 or U2 Genesis to a miniroot is highly undesirable
> as it hardly works in live environments Woudl strongly suggest
> avoiding this at all costs

Can't we just produce a patch for SUNWicda? Who owns the delivery of 
that code to the mini-root?

-- Peter

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3249 bytes
Desc: S/MIME Cryptographic Signature
URL: 
<http://mail.opensolaris.org/pipermail/install-discuss/attachments/20061017/8c15c955/attachment.bin>

Reply via email to