Solaris 11 Repository Pkg Error

Traceback (most recent call last):

File "/usr/lib/python2.6/vendor-packages/pkg/client/api.py", line 1079, in __plan_op self._img.make_install_plan(**kwargs)
File "/usr/lib/python2.6/vendor-packages/pkg/client/image.py", line 4288, in make_install_plan reject_list=reject_list) File "/usr/lib/python2.6/vendor-packages/pkg/client/image.py", line 4249, in __make_plan_common ip.plan_install(**kwargs)
File "/usr/lib/python2.6/vendor-packages/pkg/client/imageplan.py", line 419, in plan_install reject_list=reject_list)
File "/usr/lib/python2.6/vendor-packages/pkg/client/imageplan.py", line 395, in __plan_install reject_list=reject_list) File "/usr/lib/python2.6/vendor-packages/pkg/client/imageplan.py", line 370, in __plan_install_solver ignore_inst_parent_deps=ignore_inst_parent_deps)
File "/usr/lib/python2.6/vendor-packages/pkg/client/pkg_solver.py", line 442, in solve_install no_version=ret, solver_errors=solver_errors)

PlanCreationException: No matching version of system/kernel can be installed:

Reject: pkg://solaris/system/kernel@0.5.11,5.11-0.175.1.2.0.5.2:20121207T172633Z

Reason:  Newer version pkg://solaris/system/kernel@0.5.11,5.11-0.175.1.3.0.4.2:20130102T192817Z is already installed

This version is excluded by installed incorporationpkg://solaris/consolidation/osnet/osnet-incorporation@0.5.11,5.11-0.175.1.3.0.4.2:20130102T192800Z

All errors are indented with, in most cases, the significant error being indented furthest to the right hand side.

In the above example, the requested Kernel can't be installed because a later revision is already installed and it's constrained by the 'osnet-incorporation' so it can't be "down-rev'd" to an earlier version.

Therefore, when investigating an issue, use the 'pkg history' command to print out the previous errors and look at the errors that are indented to the right.

Note that the errors themselves may be repeated for each and every package that the update has failed on, so the output may still be verbose.

But the errors are typically caused by just one or two issues, such as having the incorrect Publishers specified (too few, too many, or not accessible) or insufficient content in the Repositories.