Thanks for all the replies.. Now that I have a better understanding,
I have a really basic question.
Why is mtst dependent on osnet-incorporation.
mtst's manifest file doesn't include that dependency. And when I look
at the logs, it's actually added during pkgmogrify.
---
depend fmri=consolidation/osnet/osnet-incorporation type=require
license system-fault-management-mtst.l
license=system-fault-management-mtst.l
---
Where is this coming from?
I understand that 2 more dependencies are found using pkgdepend and
those look reasonable, but I do not understand why onset-incorporation
is needed and included when doing pkgmogrify.
Thanks,
Erwin
On 03/ 7/11 03:13 PM, James C. McPherson wrote:
On 8/03/11 09:00 AM, Shawn Walker wrote:
...
$ pfexec pkg install mtst
Creating Plan /
pkg install: No matching version of system/fault-management/mtst can be
installed:
Reject:
pkg://on-extra/system/fault-management/[email protected],5.11-0.162:20110307T150226Z
Reason: This version is excluded by installed incorporation
pkg://solaris/consolidation/osnet/[email protected],5.11-0.160:20110226T064127Z
Time to ask [email protected] what's going on here.
Dear pkg-discuss denizens, how can we install the mtst package?
You can't; the osnet-incorporation states that if you install mtst, it
must be the build 160 version of mtst. However, the only version of mtst
you have available is in the on-extra repository you have configured and
it's for build 162.
You either need to find an on-extra repository with build 160 bits in
it,
or upgrade your ON bits to build 162.
Ouch. I was unaware that we were blatting nightly extra bits
into on-extra. That explains things :(
I guess we'll have to use a file:// uri pointing directly at
the 160 snapshot instead.
thankyou for clue-ing me in,
James
--
Oracle
http://www.jmcp.homeunix.com/blog
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
