User's Guide

"PB_Sept_2007,r=1.0,a=HP-UX_B.11.23_IA/PA,v=HP".
* Package Phase succeeded.
======= 08/30/07 16:25:13 EST END swpackage SESSION
With swlist, you can verify that all of the patches are now contained within the bundle:
# swlist -d @ /var/opt/ignite/depots/Rel_B.11.23/patches
# Initializing...
# Contacting target "test"...
#
# Target: test:/var/opt/ignite/depots/Rel_B.11.23/patches
#
#
# Bundle(s):
#
PB_Sept_2007 1.0 backup commands patches for Sept 2007
To continue the example, assume you missed a patch from the bundle that you created and you still
need to add it in. In this case, you need to use the –B option in a similar command to what was
used to create the bundle initially. Therefore, after you copy in the latest ls patch PHCO_33976,
you have the following in the depot:
# swlist -d @ /var/opt/ignite/depots/Rel_B.11.23/patches
# Initializing...
# Contacting target "test"...
#
# Target: test:/var/opt/ignite/depots/Rel_B.11.23/patches
#
#
# Bundle(s):
#
PB_Sept_2007 1.0 backup commands patches for Sept
2007
#
# Product(s) not contained in a Bundle:
#
PHCO_33976 1.0 ls(1) cumulative patch
You can then run make_bundles again
10
but this time we can’t use the –b option because we
want all of the patches in the depot to be placed into the bundle. To do that we need to use the –B
option instead, as –b only operates on product filesets not currently in a bundle.
make_bundles -B -i -n "PB_Sept_2007" \
> -t "backup commands patches for Sept 2007" \
> -r 1.1 /var/opt/ignite/depots/Rel_B.11.23/patches
======= 08/30/07 16:40:40 EST BEGIN swpackage SESSION
* Session started for user "root@test".
10
The reason for specifying -r 1.1 is to identify a collection of patches by a unique bundle specification composed of the
bundle name and revision. Revision 1.0 of the bundle PB_July_2004 does not include PHCO_30150; revision 1.1 does
include PHCO_30150. If the option -r 1.0 were specified, the original bundle would be replaced.
28