[pca] Patch pre-requisites
Glenn Satchell
glenn.satchell at uniq.com.au
Wed Jun 15 08:53:38 CEST 2011
Those other patches may have been superceded or obsoleted by newer
patches, and perhaps the superceded patches are already installed. Try
searching the patchdiag.xref file for the various patch numbers (without
revisions), eg
egrep '108528|117000|128624' /var/tmp/patchdiag.xref
regards,
-glenn
> Glenn,
> That seems to provide a bit more detail, which seems to make sense had
> I
> not seen the patchinfo file. I ran the pca command against the patch
> without a revision (see below) and then ran the same command against the
> dependencies to see if they had any pre-requisites (below). It seems to
> show one requirements (117350-62) but not the others. Any ideas.
> *PATCH_REQUIRES="108528-29 117000-05 117350-62"*
>
> pca -l 127721
> Patch IR CR RSB Age Synopsis
> ------ -- - -- --- ---
> -------------------------------------------------------
> 128624 -- < 16 RS- 116 SunOS 5.8: LDAP2 client, libc, libthread and libnsl
> libraries patc
> 117350 28 < 62 RS- 784 SunOS 5.8: kernel patch
> 127721 -- < 06 RS- 64 SunOS 5.8: kernel patch
>
> pca -l 128624
> Patch IR CR RSB Age Synopsis
> ------ -- - -- --- ---
> -------------------------------------------------------
> 128624 -- < 16 RS- 116 SunOS 5.8: LDAP2 client, libc, libthread and libnsl
> libraries patc
>
> pca -l 117350
> Patch IR CR RSB Age Synopsis
> ------ -- - -- --- ---
> -------------------------------------------------------
> 128624 -- < 16 RS- 116 SunOS 5.8: LDAP2 client, libc, libthread and libnsl
> libraries patc
> 117350 28 < 62 RS- 784 SunOS 5.8: kernel patch
>
> pca -l 127721
> Patch IR CR RSB Age Synopsis
> ------ -- - -- --- ---
> -------------------------------------------------------
> 128624 -- < 16 RS- 116 SunOS 5.8: LDAP2 client, libc, libthread and libnsl
> libraries patc
> 117350 28 < 62 RS- 784 SunOS 5.8: kernel patch
> 127721 -- < 06 RS- 64 SunOS 5.8: kernel patch
>
>
>
> On Mon, Jun 13, 2011 at 6:09 PM, Glenn Satchell
> <glenn.satchell at uniq.com.au>wrote:
>
>> There is some slight differences here.
>>
>> When you give pca the patch *and* the revision number it assumes that
>> you
>> want information about *only* that one patch.
>>
>> If you the patch number *without* the revision, then it looks up the
>> patch
>> and dependencies in patchdiag.xref and gives all to you.
>>
>>
>> > $ pca -l 142341
>> >
>> > Is that what you wanted?
>>
>> > Below is the command and the results. According to this no
>> dependence.
>> > pca -l 127721-03
>>
>> Try using
>>
>> pca -l 127721
>>
>> regards,
>> -glenn
>>
>>
>>
>> On 06/14/11 03:28, Fred wrote:
>>
>>> Does the system you're running pca on already meet or exceed the other
>>> unlisted requirements for that kernel patch? Remeber that pca is
>>> basically telling you "This is what I will install, in this order, for
>>> the patch you specify".
>>>
>>> Fred
>>>
>>> On Mon, Jun 13, 2011 at 1:03 PM, little help <littlehelphere at gmail.com
>>> <mailto:littlehelphere at gmail.com>> wrote:
>>>
>>> Actually I did a little more digging on this and the "-l" option does
>>> not seem to show the dependencies. For example I ran the command
>>> against a kernel patch
>>>
>>> Below is the command and the results. According to this no
>>> dependence.
>>> pca -l 127721-03
>>>
>>> Patch IR CR RSB Age Synopsis
>>> ------ -- - -- --- ---
>>> -------------------------------------------------------
>>> 127721 -- < 06 RS- 63 SunOS 5.8: kernel patch
>>>
>>> I then untarred the actual patch and looked at the patchinfo file.
>>> You can see the patch requires three other patches. So now I guess
>>> I am back to the beginning. Any ideas how to get details on the
>>> dependencies for a patch? Thanks.
>>> more patchinfo
>>> PATCHINFOVERSION="1.0"
>>> PATCHID=127721-03
>>> PATCH_CORRECTS='Automate-1.0'
>>> PATCH_ARCH='sparc'
>>> PATCH_OS='SunOS'
>>> PATCH_OSRELEASE='5.8'
>>> PATCH_PROPERTIES='clientroot clientusr rebootimmediate singleuser'
>>> *PATCH_REQUIRES="108528-29 117000-05 117350-62"*
>>> PATCH_OBSOLETES="108727-26 111439-03 112325-01 114671-04 116959-21"
>>>
>>>
>>>
>>> On Mon, Jun 13, 2011 at 10:37 AM, little help
>>> <littlehelphere at gmail.com <mailto:littlehelphere at gmail.com>> wrote:
>>>
>>> Fred,
>>> Seems to be right - thanks for the tip.
>>>
>>> On Fri, Jun 10, 2011 at 1:28 PM, Fred <fchagnon at gmail.com
>>> <mailto:fchagnon at gmail.com>> wrote:
>>>
>>> You can determine the dependencies of a single patch by
>>> supplying the patch ID in the ARGS list on the command line.
>>> For example:
>>>
>>> $ pca -l 142341
>>>
>>> Is that what you wanted?
>>>
>>>
>>>
>>> On Fri, Jun 10, 2011 at 10:55 AM, little help
>>> <littlehelphere at gmail.com <mailto:littlehelphere at gmail.com>>
>>>
>>> wrote:
>>>
>>> I had a quick question about the pre-requisites when
>>> installing one patch. I know pca determines dependence,
>>> etc and installs patches in that order. However, how do
>>> you do this for one single patch. For example - I want
>>> to install
>>> 109326-17 : libresolv.so.2, in.named and BIND9 patch
>>> Now libresolv.so.2 has C dependencies. When I do a full
>>> pca check for my host the C patches come right after the
>>> patch for patchadd. However, there are about 20+
>>> patches before I get tot he libresolv patch. Are all
>>> these patches dependencies? I don't see how. I look at
>>> the readme file for the libresolv patch and do not see
>>> anything at all about dependencies. Is there a way to
>>> check what requirements this patch needs from pca -
>>> perhaps a flag, etc? Thanks.
>>>
>>>
>>>
>>>
>>> --
>>> Fred Chagnon
>>> fchagnon at gmail.com <mailto:fchagnon at gmail.com>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Fred Chagnon
>>> fchagnon at gmail.com <mailto:fchagnon at gmail.com>
>>>
>>
>>
>
More information about the pca
mailing list