On 02/12/11 04:33 PM, Janie Lu wrote:
I'm hitting errors when I try to build an AI ISO image from a gate
based on nv_159.
Two questions on this. The first is for the Caiman team. The second is
for the pkg team.
_
BACKGROUND_
Our gate was sync'd with onnv-clone on 2/7/11, making our ON base
nv_159. An "hg tags" confirms this showing "onnv_159" as the most recent
tag.
_
QUESTION 1 (Caiman Team)_
Using DC with our packages based on nv_159 is failing because there is
no "entire" nv_159 version yet available. The latest version of "entire"
that is currently available at http://ipkg.sfbay.sun.com/dev/solaris is
nv_158. Therefore if I specify to install
"pkg:/[email protected],5.11-0.159" in the DC manifest, I hit the following
error:
The following pattern(s) did not match any packages in the current catalog.
Try relaxing the pattern, refreshing and/or examining the catalogs:
pkg:/[email protected],5.11-0.159
However, I see no choice but to specify that the nv_159 version of
entire be installed. Since the gate is based on nv_159 some of the
packages will be at the nv_159 version. (e.g. SUNWcs, SUNWcsd).
Therefore if I specified to install entire nv_158, my gate packages at
the nv_159 version would NOT be installed. What am I missing?
Don't specify "entire" at all in your DC manifest. Just remove it. You
can't use entire@anything if you want to use a mismatched ON from the
rest of the WOS.
Of course, this falls out from the general way of testing ON in which
entire is uninstalled. See usr/src/pkg/README.pkg.
_QUESTION 2 (pkg Team)_
Although our gate is based on nv_159, our gate packages have "160" in
the package names. Why is this? nv_160 has not even closed yet.
pkg://on-nightly/[email protected],5.11-0.160:20110210T084110Z
pkg://on-nightly/[email protected],5.11-0.160:20110210T084110Z
Nothing to do with pkg, the version comes from the ON gate in
/ws/onnv-gate/usr/src/Makefile.buildnum. This is described in ON in
usr/src/pkg/README.pkg.
ON changes the verison when it *opens* a build, because those bits will
be contributing to build 160. 159 is done, so the bits between 159 and
160 will never be in 159.
liane
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
