How to install patch

[Musa I. S.]

Hello,
I downloaded a patch bundle in gzip format. Now I have gunzipped and its in .tar format. How do i proceed?

[Jeeshan]

untar that .tar file
and then you may see the create depot script. run it. it will create a depot folder.then run swinstall

#swinstall -s

[James R. Ferguson]

Hi:

At this point you should have a tar ball that contains a script called something like '/tmp/create_depot_hp-ux_11'. Do:

# tar -xvf /tmp/hpux*.tar

...untar the tar ball

# /tmp/create_depot_hp-ux_11

...run this to create a patch depot

# swinstall -s /tmp/depot -x autoreboot=true -x patch_match_target=true

...will reboot your server if required

Regards!

...JRF...

[Musa I. S.]

I got the error attached. The installation didn't complete.

[James R. Ferguson]

Hi:

Add the '-x enforce_dependencies=true':

# swinstall -s /tmp/depot -x autoreboot=true -x patch_match_target=true -x enforce_dependencies=true

This should be the default setting and thus I didn't have you specify it. Examine your '/var/adm/sw/defaults' file. It would appear that is specifies 'enforce_dependencies=false'.

Regards!

...JRF...

[Bob E Campbell · Accepted solution]

enforce_dependencies=true is a *requirement* for happy HP-UX swinstalls, but is not your fundamental problem. You are trying to install a single patch when HP-UX really wants you to use multi-patch depots.

Go to https://www.hp.com/go/swa and install the most recent version of Software Assistant. Then run the following:

1. swa report -a CHAIN=PHCO_36744

2. swa get -t /var/tmp/mydepot

3. Review the report found in /var/tmp/mydepot/readBeforeInstall.txt

4. Install

swinstall -s /var/tmp/mydepot -x autoreboot=true -x patch_match_target=true

5. Remove old depot

swreg -u -l depot /var/tmp/mydepot
rm -rf /var/tmp/mydepot

[Musa I. S.]

The link is not loading. What are the pros and cons if I use the 'Enforce...' option?

[Bob E Campbell]

Use the enforce options with swcopy when needed.

HP *generally* does not create dependencies without cause. Unless you want to go nuts working out load orders (and recursive deps are known) you want to use SWA or the ITRC (http://www.itrc.hp.com) Patch Database to manage dependencies and help you build a depot.

If you choose to ignore them the bad things will depend on what you "broke". It can range from failure to rebuild a kernel to failure to boot.

The SWA link is working for me just now. It is available from Software Depot, just go to hp.com and search if needed.

[James R. Ferguson]

Hi (again):

It is often appropriate to use '-x enforce_dependencies=false' when copying patches into a depot with 'swcopy'.

At your own risk, use this during a 'awinstall' session. During software installation, you want 'enforce_dependencies=true' (the standard default).

Setting the option to *false* is done during 'swcopy' operations to *defer* dependency checking until later (during an actual 'swinstall'). That is, you can build a smaller software depot if you know that dependencies will be checked and resolved at installation. During a 'swinstall' session, the union of the depot's contents and you server IPD (installed product database) is used for depenedency checking unless you specifically (and unwisely) say otherwise by setting 'enforce_dependencies=false'.

Regards!

...JRF...

[Dennis Handly]

>I got the error attached.

What errors? There was just the output from the swcopy and swverify then the depot was built.

>JRF: Add the '-x enforce_dependencies=true'

But you want false for swcopy.

>JRF: It is often appropriate to use '-x enforce_dependencies=false' when copying patches into a depot with 'swcopy'.

That's exactly what the log implied.

[Musa I. S.]

The problem has been resolved. First, we installed the old version of the patch. it complained about an IPFilter, which we installed. There was also the error with libstream.a. We copied it from another PA-RISC server and everything went well.

Thanks very much Friends.

[James R. Ferguson]

HI:

> Dennis: That's exactly what the log implied.

Yes, and for whatever reason I misread the header in the log thinking that the session was an install and not a copy. Missing that, it didn't make sense to me either in my initial post. Sorry for the confusion, Musa.

Regards!

...JRF...

[Dennis Handly]

>There was also the error with libstream.a. We copied it from another PA-RISC server and

Why not download the aC++ runtime patch for libstream? PHSS_35055

[Bob E Campbell]

I am glad to hear that you have worked through the issue, but suggest you take a moment to check state.

Use the command:

# swverify \*

and track what software and patches SD-UX feel are out of sync with the IPD. This should hopefully be a short list and you can make it a priority to load. If it seems like everything is broken, consider a full reinstall at the next update. I am funny about systems being in a *known*, good state.