On 11/19/10 15:01, Janie Lu wrote:
Thanks for the detailed response Bart. Please see responses inline.
-------- Original Message --------
Subject: Re: [pkg-discuss] [caiman-discuss] DC build error when
adding pkg
Date: Fri, 19 Nov 2010 11:53:55 -0800
From: Bart Smaalders <[email protected]>
Organization: Oracle
To: [email protected], caiman-discuss
<[email protected]>
On 11/19/10 09:14, Keith Mitchell wrote:
> It seems very strange that the SUNWarc package isn't resolvable by IPS
> for this situation. I can't see why that would be; perhaps someone on
> pkg-discuss can help here.
>
> - Keith
You have a rather tortured set of publishers
Don't I know it. ;) But I don't see how else the publishers can be
categorized if one wants install "pkg:/sunstudio12u1" but is sync'd with
build nv_151 or later after the opensolaris.org-->solaris publisher
change occurred. The issue I see is that some packages are available in
the solaris publisher and others (like sunstudio12u1) are still only
available in the opensolaris.org publisher. Therefore aren't both
publishers required to be listed in this situation?
Specifics: Since my gate is sync'd with nv_151a I therefore need to list
the "solaris" repo (ipkg.sfbay/dev/solaris) as an alternate publisher
(correct?). But sunstudio12u1 isn't available in that repo. It is
available in the "opensolaris.org" repo (http://ipkg.sfbay.sun.com/dev)
and thus that also needs to be added too. Please let me know if that's
not right.
at different version
levels, which has led to all sorts of problems.
The reason DC won't work:
--------------------------
yf-on-nightly (and extra) has packages only for 151
There's something strange with that then. yf-on-nightly packages were
built from a gate sync'd with nv_151a not 151. Does 151a = 151.0.1? I
had assumed so.
Here is the yf gate's "hg log" output showing it is sync'd with nv_151a
(there are nv_151a changesets):
http://re.west/gates/yf/yf-onnv-gate/log.out
publisher on-nightly
solaris has packages through 151, 151.0.1, 152,
publisher solaris
The first publisher in the search order to offer a package of
the desired name is selected. This prevents interleaved
dynamic composition of publishers to obtain the desired versions.
In this case, the first publisher to provide entire is on-nightly
on-nightly does not provide entire. I've never seen 'entire' built when
I run a nightly build of S11.
The first publisher to provide entire would be solaris
(http://ipkg.sfbay.sun.com/dev/solaris), which would pick up the latest
available version of 'entire' - since I don't want the latest version, I
want 151a which the yf gate is sync'd with, I specified for it to
install entire at version 151.0.1.
But look at your repository in a browser:
http://mpkpen-ai-3.sfbay/yf-on-nightly/en/catalog.shtml
Your packages look like this:
0.5.11,5.11-0.151:20101117T014244Z
If you want 151.0.1 ON packages, you need to build with
ONNV_BUILDNUM set to that (please complain to ON gatekeepers;
they own this bit of magic.).
- Bart
--
Bart Smaalders Solaris Kernel Performance
[email protected] http://blogs.sun.com/barts
"You will contribute more with mercurial than with thunderbird."
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
