topic Re: creating an sd patch in Operating System - HP-UX

creating an sd patch

Timothy Cole_1 — Fri, 16 Apr 2004 16:33:43 GMT

I'm trying to create a patch for an existing HP product (in this case, Mozilla). I'm able to create the patch sucessfully, but I can't seem to install it; I get an error indicating that the ancestor fileset was not found on the target.

Perhaps I am specifying the ancestor fileset incorrectly (Mozilla.MOZ-COM,fr=1.4.0.01.00,v=HP)?

Are there other properties I also need to set before the patch will match?

Re: creating an sd patch

Scot Bean — Fri, 16 Apr 2004 17:17:54 GMT

Sounds interesting. Are you using 'swpackage' to build this patch?

Here is a document that describes how to specify patches in SD, with an example:

http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90789/B2355-90789_top.html&con=/hpux/onlinedocs/B2355-90789/00/00/28-con.html&toc=/hpux/onlinedocs/B2355-90789/00/00/28-toc.html&searchterms=patch&queryid=20040416-161540

If you are still stuck, post your specification file.

Re: creating an sd patch

Timothy Cole_1 — Fri, 16 Apr 2004 17:58:48 GMT

Hmm, unless I'm missing something obvious, I'm doing it correctly according to the document you linked.

Here's the PSF I'm using (too bad this thing eats indention :/). Maybe there's something important I'm missing that I've been staring at this too long to see..

product
tag Mozilla_Fixes
title "Mozilla Fixes"
description "Various fixes for Mozilla"
revision 1.0
os_name HP-UX
os_release ?.11.*
machine_type *
is_patch true
os_version *

fileset
tag MOZ-COM
ancestor Mozilla.MOZ-COM,r=1.4.0.01.00,v=HP
revision 1.0
is_patch true
is_sparse true

directory /patches/mozilla-fixes=/opt/mozilla
file -u 022 -g bin -o bin en-US.jar chrome/en-US.jar
end

end

Re: creating an sd patch

Timothy Cole_1 — Fri, 16 Apr 2004 17:59:21 GMT

And, yes, I'm using swpackage :)

Re: creating an sd patch

Scot Bean — Fri, 16 Apr 2004 18:27:59 GMT

You are missing the 'architecture' tag at the product level. Specify it to match the architecture tag for Mozilla.

Try that, see if works.

Re: creating an sd patch

Timothy Cole_1 — Mon, 19 Apr 2004 11:33:24 GMT

I added the architecture attribute (taken directly from Mozilla's INDEX), but still no luck. :/

* Reading source for file information.
NOTE: The patch fileset "Mozilla_Fixes.MOZ-COM,r=1.0" may only
be installed upon a previously installed base fileset. The
specification for this base fileset is
"Mozilla.MOZ-COM,r=1.4.0.01.00,v=HP". Since there is no
fileset on the target or selected from the source which
matches this specification, fileset
"Mozilla_Fixes.MOZ-COM,r=1.0" will be excluded.

Re: creating an sd patch

Anil C. Sedha — Mon, 19 Apr 2004 11:41:50 GMT

Hi,

Your are specifying "ancestor" in your fileset subset which is causing it to find the base fileset first.

Try removing that and putting in just the title for the fileset.

title Mozilla patch

let us know if that worked.

Regards,
Anil

Re: creating an sd patch

Timothy Cole_1 — Mon, 19 Apr 2004 12:09:50 GMT

I don't understand -- isn't ancestor a required attribute for a patch fileset (particularly a sparse one)?

Re: creating an sd patch

Anil C. Sedha — Wed, 21 Apr 2004 13:49:18 GMT

It is not a required attribute.

Re: creating an sd patch

Timothy Cole_1 — Thu, 22 Apr 2004 17:03:37 GMT

Are you sure? When I omit the ancestor attribute, I get this:

NOTE: The patch fileset "PTDS_Mozilla_Fixes.MOZ-COM,r=1.0" may only
be installed upon a previously installed base fileset. The
specification for this base fileset is "". Since there is no
fileset on the target or selected from the source which
matches this specification, fileset
"PTDS_Mozilla_Fixes.MOZ-COM,r=1.0" will be excluded.

Re: creating an sd patch

Bharat Katkar — Sat, 24 Apr 2004 03:36:47 GMT

Timothy,
Try copying the patch to the default SD depot and then install.
Hope it works.

Re: creating an sd patch

Timothy Cole_1 — Tue, 27 Apr 2004 16:45:21 GMT

Since I am pressed for time, what I will do is create normal filesets that have the fileset being patched as a prerequsite, which appears to work.

That does mean the fileset specification I was using with "ancestor" was correct, since it matches fine using "prerequsite". Does ancestor have any other special requirements for matching?