Re: [caiman-discuss] [pkg-discuss] SUNWcs@143 has nv_145 dependencies?

[Janie Lu]

On 09/27/10 10:50, Shawn Walker wrote:
On 09/27/10 09:52 AM, Janie Lu wrote:


On 09/27/10 08:48, Keith Mitchell wrote:
On 09/26/10 05:06 PM, Janie Lu wrote:
On 9/16/10 11:16 AM, Keith Mitchell wrote:
On 09/16/10 10:54 AM, Janie Lu wrote:

[...]
The changes I made to both the default DC manifest and the AI
manifest are the same:

1. Specified 3 publishers in this order:
<main url="http://<machine>.sfbay/yf-on-nightly/"
publisher="on-nightly"/> <<<---Our repo.redist based on nv_143
<main url="http://<machine>.sfbay/yf-on-extra/"
publisher="on-extra"/> <<<---Our repo.extra based on nv_143
<main url="http://ipkg.sfbay/dev/"; publisher="opensolaris.org"/>
2. Deleted "entire" pkg from list of pkgs to install.

Looking at the /tmp/install_log, the 147 packages are expected
(anything starting with "pkg://opensolaris.org" is coming from
ipkg, and will be @147). The interesting, and odd ones, are the
ones coming from nv_145, which makes no sense to me.

These nv_145 packages are causing my DC build of a debug nv_143 AI
ISO image to fail. FYI I was able to build a non-debug AI ISO image
using your suggestions (thanks!), but now when I try to build a debug
ISO with the same suggestions implemented it fails due to five nv_145
dependencies.

-------------------------------------------------------------------------------------------------------------------- 


Error in my DC build log is below.
(Full log at:
http://re.west/gates/yf/builds/ONNV/yf-onnv-14.143/images/detail-log-2010-09-26-00-38-16-FAIL) 



exec command: /usr/bin/pkg -R
/rpool/DC-yf-onnv-14/build_data/pkg_image install --no-index
ent...@0.5.11,5.11-0.143 SUNWcsd SUNWcs
Planning for install failed:
Use -v option for more details
pkg: No solution was found to satisfy constraints
--------------------------------------------------------------------------------------------------------------------- 



Output below is from running the failed "pkg_image install" command
above with the verbose flag. This exposes five nv_145 dependencies.
(Full log at:
http://re.west/gates/yf/builds/ONNV/yf-onnv-14.143/images/ROOT_ERROR)
SUNWcs
*pkg://on-nightly/sun...@0.5.11,5.11-0.143*:20100924T102057Z
require: consolidation/osnet/osnet-incorporation
Requires one
of:pkg://on-nightly/consolidation/osnet/osnet-incorporat...@0.5.11,5.11-0.143:20100924T102039Z 


require:pkg:/sun...@0.5.11-0.143
Requires one
of:pkg://on-nightly/sun...@0.5.11,5.11-0.143:20100924T102057Z
require:pkg:/library/libte...@1.6.0-0.143
Requires one
of:pkg://on-nightly/library/libte...@1.6.0,5.11-0.143:20100924T102834Z
*require:pkg:/library/libx...@2.7.6-0.145
* FAIL: No matching packages found
Ruled
outpkg://opensolaris.org/library/libx...@2.7.6,5.11-0.146:20100813T050304Z 

because: Suitable required
dependencypkg:/system/libr...@0.5.11,5.11-0.146 cannot be found
Ruled
outpkg://opensolaris.org/library/libx...@2.7.6,5.11-0.147:20100827T064037Z 

because: Suitable required
dependencypkg:/system/libr...@0.5.11,5.11-0.147 cannot be found
Ruled
outpkg://opensolaris.org/library/libx...@2.7.6,5.11-0.148:20100911T162310Z 

because: Suitable required
dependencypkg:/system/libr...@0.5.11,5.11-0.148 cannot be found
Ruled
outpkg://opensolaris.org/library/libx...@2.7.6,5.11-0.145:20100730T015634Z 

because: Suitable required
dependencypkg:/system/libr...@0.5.11,5.11-0.145 cannot be found
*require:pkg:/library/security/trous...@0.3.4-0.145*
FAIL: No matching packages found
Ruled
outpkg://opensolaris.org/library/security/trous...@0.3.4,5.11-0.146:20100813T050853Z 

because: Suitable required
dependencypkg:/system/libr...@0.5.11,5.11-0.146 cannot be found
Ruled
outpkg://opensolaris.org/library/security/trous...@0.3.4,5.11-0.145:20100730T020204Z 

because: Suitable required
dependencypkg:/system/libr...@0.5.11,5.11-0.145 cannot be found
Ruled
outpkg://opensolaris.org/library/security/trous...@0.3.4,5.11-0.148:20100911T162834Z 

because: Suitable required
dependencypkg:/system/libr...@0.5.11,5.11-0.148 cannot be found
Ruled
outpkg://opensolaris.org/library/security/trous...@0.3.4,5.11-0.147:20100827T064838Z 

because: Suitable required
dependencypkg:/system/libr...@0.5.11,5.11-0.147 cannot be found
*require:pkg:/library/z...@1.2.3-0.145*
FAIL: No matching packages found
--------------------------------------------------------------------------------------------------------------------- 



Any idea what the issue is?

At build time, pkgdepend will use the build system to automatically
generate dependencies. I'm guessing your build system is running 145 -
try building on a 142 or 143 BE.

I ran this on nv_143. Actually, I ran through this exercise on another
machine running nv_143 and hit the same error on both.

# cat /etc/release
Oracle Solaris Next Development snv_143 SPARC
Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved.
Assembled 02 July 2010
# uname -a
SunOS dt92-418 5.11 snv_143 sun4v sparc sun4v Solaris


Although I'd have expected that to affect both a debug and a non-debug
build.

pkg-disc...@opensolaris.org would be able to help more with these sort
of issues, as well.

Thanks, I've added that alias to this thread now as I'm not clear on
whether this is a pkg or DC issue.

Summary of the Situation:
When attempting to create a debug AI ISO using DC on a BE running
nv_143, with DC manifest specifying to install ent...@0.5.11,5.11-0.143,
the build fails because it says SUNWcs requires five packages at nv_145.

I think you misunderstood; you need to rebuild on-nightly on a system 
with build 143.

The pkg build process creates dependencies based on the OS version that 
the *build machine* is running? That doesn't seem right.

Instead, shouldn't pkg be using the OS version that the *source code* is 
based on when creating packages from that code? (This info is available 
in the macro "ONNV_BUILDNUM" in usr/src/Makefile.buildnum)


GIVEN THAT:
        SUNWcs requires packageX.
        Developer workspace is based on nv_143.
        Developer builds his workspace on a machine running nv_145.


CURRENT BEHAVIOR:
       sun...@143 depends on packa...@145.
       Why:  IPS uses the build machine OS version to set package
                   dependencies, regardless of the source code's OS 
version.

SHOULD BE:
       sun...@143 depends on packa...@143.
       Why:  IPS looks at the source code being built to determine the OS
                   version and then sets dependencies accordingly.


Let me know if I'm not understanding the situation correctly.
Janie



From the output above, the package:

pkg://on-nightly/sun...@0.5.11,5.11-0.143*:20100924T102057Z

...is the one that has requirements on build 145+ packages.

If you look at the package manifest for SUNWcs, I imagine you'll find 
that it contains dependencies you don't expect.

-Shawn
_______________________________________________
caiman-discuss mailing list
caiman-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss