topic Re: Patching dependancies - the chase in Operating System - HP-UX

Patching dependancies - the chase

JHL_1 — Wed, 14 Aug 2002 21:37:36 GMT

Ok, I'm finding out that I need a whole series of patches for a network card. I download them, untar them, run the "sh" against them. Great, I'm excited. Then I run the swcopy command and it works ....for the first few.

Then I begin getting errors about dependancies but I know when I went to the site to download the patches that the dependancies were included.

I've got over 20 patches here.

1) Is there a "global" swcopy for XXX.depot patch files?
2) If I did in fact download the the dependancies (and I did - I checked) then why do I still get errors like the following?

"usimagen:/downloads/hppatches/netpatchdepot".
NOTE: The software "PHKL_24729" was successfully marked, but it
depends on the following software items which could not be
found in the source. However, these items may already be in
the target. This will be checked during the Analysis Phase:
PHKL_18543.CORE2-KRN,fr=*,fa=HP-UX_B.11.00_32,v=HP
PHKL_18543.CORE2-KRN,fr=*,fa=HP-UX_B.11.00_64,v=HP
* Source: /downloads/hppatches/PHKL_24729.depot
* Targets:
usimagen:/downloads/hppatches/netpatchdepot
* Software selections:
PHKL_24729.CORE2-KRN,r=1.0,a=HP-UX_B.11.00_32/64,v=HP,fr=1.0,fa=HP-
UX_B.11.00_32
PHKL_24729.CORE2-KRN,r=1.0,a=HP-UX_B.11.00_32/64,v=HP,fr=1.0,fa=HP-
UX_B.11.00_64
* Selection succeeded.

* Beginning Analysis
* Session selections have been saved in the file
"/.sw/sessions/swcopy.last".
ERROR: "usimagen:/downloads/hppatches/netpatchdepot": The software
dependencies for 2 products or filesets cannot be resolved.
* The analysis phase failed for
"usimagen:/downloads/hppatches/netpatchdepot".
* Analysis had errors.

NOTE: More information may be found in the agent logfile (location
is usimagen:/downloads/hppatches/netpatchdepot/swagent.log).

======= 08/14/02 17:36:05 CDT END swcopy SESSION (non-interactive)

Re: Patching dependancies - the chase

George Petrides_1 — Wed, 14 Aug 2002 21:58:13 GMT

If you use the swcopy GUI you can change the options not to enforce dependencies. Of course you can do that with the command line but I don't remember the option and don't have a UX machine at home. If you find the option with man swcopy, then you can do the 'global' thing with a small script that can do:
for PATCH in `ls *.depot`
do
PATCH_NAME="`echo $PATCH | awk -F'.' '{print $1}'`"
swcopy -s ...DIR_PATH../$PATCH $PATCH_NAME @ .../DEPOT_PATH OPTION_TO_IGNORE_DEPENDENCIES
done

Re: Patching dependancies - the chase

Trond Haugen — Thu, 15 Aug 2002 06:04:42 GMT

The option to swcopy you need is '-x enforce_dependencies=false'.

Regards,
Trond

Re: Patching dependancies - the chase

Michael Tully — Thu, 15 Aug 2002 06:22:26 GMT

Make sure you create an ignite backup before loading any patch, particularly when the system requires either a reboot/kernel changes.

Here is an example.
# /opt/ignite/bin/make_tape_recovery -x inc_entire=vg00 -I -v -a /dev/rmt/0mn

Re: Patching dependancies - the chase

melvyn burnard — Thu, 15 Aug 2002 07:12:37 GMT

So the question that you are asking is?:
While running a swcopy, I get an error regarding dependencies. How do I fix?

Well as it is asking about PHKL_18543, you must ensure this IS on your system.
However, to do the copy, just mark the enforce_dependencies to be equal to false.

When you come to do the swinstall, ensure the enforce_dependencies is set to true, and the patch should then check for PHKL_18543 , find it and install ok.

But as said previously, ensure you have a good backup before proceeding. "A stitch in time saves nine" as the old proverb goes

Re: Patching dependancies - the chase

Gordon Brown_4 — Thu, 15 Aug 2002 08:16:54 GMT

Hi JHL,

I have expereinced the exact same problem as yourself before. I think it was actually with the same patch (PHKL_18543).

I use swcopy as follows, for example:

swcopy ???s /tmp/Patches/PHKL_XXXX.depot -x enforce_dependencies=false \* @ /var/spool/patchdepot

swcopy command does not check which patches are already installed on the server when checking for resolved patch dependencies. It checks which other patches are in the depot for dependencies. If your patch dependencies are already installed on the system (and therefore not required in the depot), set the enforce_dependencies parameter to false.

Hope this is of help,

Cheers,
Gordon

Re: Patching dependancies - the chase

James R. Ferguson — Thu, 15 Aug 2002 12:11:18 GMT

Hi:

As already noted, you can add the option '-x enforce_dependencies=false' to your 'swcopy' to allow the patch collection to be bundled even if all patch dependencies are not met.

You may elect to 'swcopy' patches that you already have installed merely to affect a successful 'swcopy' and subsequently allow 'swinstall' to skip them if they are already installed.

The choice is yours, given that you *do* enforce dependencies during the 'swinstall' session. In that case, any dependencies satisfied by their presence as installed and configured entities on the server yield as successful installation.

Regards!

...JRF...

The new ITRC patch interface greatly improves dependency collection.

Re: Patching dependancies - the chase

Dave Unverhau_1 — Fri, 16 Aug 2002 17:23:36 GMT

JHL,

You likely already have PHKL_18543 installed on the system on which you plan to apply these patches. However, under some circumstances, you may find that you need to reapply this patch. This is because PHKL_18543 (aka "the LITS patch) affects many filesets that comprise core portions of the operating system, as well as optional software filesets.

If this is the only patch about which you are receiving complaints (very possible), I would go ahead and download this patch and add it to the depot.

The important thing to do is to make sure that when you run swinstall, you DO NOT alter the default options of reinstall=false or reinstall files=false. If you set either of these =true, you stand a very good chance of rendering your system unbootable (particularly if your root filesystem is configured to use VxFS, but still possible otherwise).

As long as the reinstall options are left at the default setting of false, this patch is safe to reapply (and may be necessary to reapply). This is because it's possible to have installed some optional system software that should be patched by the LITS patch, after this patch was applied. In this case, those filesets would be unpatched, since they weren't available to be patched when the LITS patch was first installed. (That got kind of wordy, but it's a confusing situation for many!)

I hope this helps!

Dave

Re: Patching dependancies - the chase

harry d brown jr — Fri, 16 Aug 2002 20:58:30 GMT

You should use the CUSTOM PATCH MANAGER, which will eliminate this issue! Just follow the instructions.

live free or die
harry

Re: Patching dependancies - the chase

harry d brown jr — Fri, 16 Aug 2002 23:35:30 GMT

Great topic:
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x96b70bce6f33d6118fff0090279cd0f9,00.html
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x316efd3f91d3d5118ff40090279cd0f9,00.html

Great help in finding them:
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x1e6f84534efbd5118ff40090279cd0f9,00.html

live free or die
harry