Glenn Lagasse wrote:
> That doesn't look nearly correct enough. Where are all the other
> updates from on-nightly that should be applied?
pkg install -nv $(pkg list -H consolidation/\*-incorporation | awk '{print
$1}')
save the output to a file, and look for FAIL: in there. If you need help
interpreting, stick the log up on cr.os.o and point us at it.
> If I try to install my new beadm package from on-nightly I get:
>
> [1] r...@praetorian> pkg -R /a install -v install/beadm
> Creating Plan /Planning for install failed:
>
>
> pkg: No matching version of install/beadm can be installed:
> pkg://on-nightly/install/[email protected],5.11-0.146:20100803T000245Z: This
> version is excluded by installed incorporation
> pkg://opensolaris.org/consolidation/install/[email protected],5.11-0.143:20100706T015509Z
>
> Now, this doesn't make any sense. Yes, beadm is listed in the
> install-incorporation in build 143. But, that was removed in build 144
> which ipkg.sfbay/dev knows about (which is my configured opensolaris.org
> publisher).
If the build 143 version of install-incorporation is installed, and you're
not attempting to upgrade it at all, then whatever constraints it includes
are in force. If you were to run "pkg install
[email protected]", then it would drag the install
consolidation forward to build 144, possibly leaving beadm behind, which
you could then upgrade freely. (Though I can't say I understand why it's
not constrained in any way.)
Danek
_______________________________________________
on-ips-dev mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/on-ips-dev
