topic Re: Need help in patch creation in Operating System - HP-UX

Need help in patch creation

Tarun Jain_1 — Mon, 02 Jun 2008 11:27:23 GMT

Hi HP-Experts,

One of the perl related library we have shipped as GA and now we want to patch it. We are creating the patch but it is not installing on the GA version. There were some problems related to some field in GA version. I am pasting the 'swlist -v' output for fileset:

============================================
fileset
tag library
software_spec CYPerl.library,r=5.0.00.0,v=Cyneta
data_model_revision 2.40
instance_id 1
control_directory library
size 420603
revision 5.0.00.0
title CYServer Perl library by Cyneta
description
mod_date Tue May 27 17:36:45 IST 2008
mod_time 1211890005
create_date Tue May 27 17:36:43 IST 2008
create_time 1211890003
architecture
machine_type
os_name
os_release
os_version
is_patch false
supersedes
category_tag
state available
is_kernel false
is_reboot false
is_packaged_in_place false
is_secure false
ancestor
media_sequence_number
partial_file
partial_pipe_size
partial_state_path
is_sparse false
is_locatable
location
dynamic_module
is_drd_safe
===============================================

Now for patch, my psf is as follows:

=======================================
vendor
tag Cyneta
title Cyneta Networks
description CYServer Perl library from Cyneta
end
product
tag PCCO_03812
title "CYServer Perl library by Cyneta"
description < description.product
revision 1.0
os_name HP-UX
os_release B.11.23
os_version *
architecture HP-UX_B.11.23_IA/PA
machine_type *
directory /opt
is_locatable true
is_patch true
vendor_tag Cyneta
fileset
tag CYLIBRARY
title "Cyneta Connection Server Perl library"
architecture HP-UX_B.11.23_IA/PA
os_name HP-UX
os_release B.11.23
os_version *
revision 1.0
machine_type *
is_patch true
ancestor CYPerl.library,r=5.0.00.0,v=Cyneta

# Files
file_permissions -m 500 -o root -g sys
....
....
....
end
end
==========================================

Though ancesotor in patch is matching to the GA package, when I install the patch on GA, it gives me dependency error. It says "CYPerl.library,r=5.0.00.0,v=Cyneta" is not installed on the machine.

Please help.

Thanks in Advance !!

Best Regards,
Tarun

Re: Need help in patch creation

Ivan Krastev — Mon, 02 Jun 2008 11:57:39 GMT

You have specified:
ancestor CYPerl.library,r=5.0.00.0,v=Cyneta

and the patch is looking for that product, installed on system.

See more for ancestors - http://docs.hp.com/en/5992-0674/ch03s03.html

regards,
ivan

Re: Need help in patch creation

Dennis Handly — Mon, 02 Jun 2008 12:27:43 GMT

Typically you just use "swlist -l fileset -a software_spec" to track this down.
Original: CYPerl.library,r=5.0.00.0,v=Cyneta

I don't see one for your patch?
ancestor CYPerl.library,r=5.0.00.0,v=Cyneta

Also, your patch has info about a bunch of fields that don't seem to be filled in in the product: os_name ...

As Ivan's document mentions, the name of the two filesets must match, be "library".

Re: Need help in patch creation

Bob E Campbell — Tue, 03 Jun 2008 21:23:59 GMT

Unless rollback and sparseness are critical I might recommend that you release an incremental version of the product and call it a "patch".

That said, the critical attributes for a patch are ancestor, is_patch, and is_sparse. Be sure to set is_sparse to true in your final patch. By convention a "category_tag" attribute is set to the value "patch".

I see enough oddities in the original product that I am kind of curious how this all works out. The four attributes that control product behavior (machine_type, os_version, os_release, and os_name) were all kept blank. While the patch looks "better", you might try once breaking the patch to match the broken product.

Re: Need help in patch creation

Tarun Jain_1 — Fri, 06 Jun 2008 12:10:57 GMT

Thanks All.

So, as Bob mentioned, I have tried with faulty patch like GA, without ARCH, mach_type, os_version etc. It worked !!

Thanks all.

Re: Need help in patch creation

Bob E Campbell — Fri, 06 Jun 2008 13:52:10 GMT

Oh dear, I was afraid that would work :-)

I do recommend that the next time a product is packaged you consider fixing up all the attributes. While it does not help with patches the Software Package Builder can do wonders with products and bundles.

http://docs.hp.com/en/5990-6771/ch01s01.html?jumpid=reg_R1002_USEN