On Thu, Feb 19, 2009 at 04:13:21PM +0000, Sean McGrath wrote: > < # grep slim_install index/full_fmri_list | grep 106: > < pkg:/slim_install at 0.1,5.11-0.106:20090131T192521Z > < > < and use that to build an ai manifest with entries like: > < > < <ai_packages> > < <package_name>slim_install at 0.1,5.11-0.106</package_name> > < </ai_packages> > > [ ... ] > > < pkg: pkg: the following package(s) violated constraints: > > < "Package entire contains constraint that requires downgrade of > installed > < pkg pkg:/SUNWtls at 0.5.11,5.11-0.107:20090212T184617Z: > > < Pkg SUNWtls: Optional min_version: 0.5.11,5.11-0.106 max > > < version: 0.5.11,5.11-0.106 defined by: pkg:/entire > > < > > < ... > > > Digging around a bit this seems to be when pkg comes along to install > the SUNWipkg package. In the code[1] it seems to check if its installing > the latest available and does so.
It doesn't actually install anything; it just refuses to move forward if the latest isn't installed. There's a bug open to make it just do the installation, but we haven't agreed on how to do that safely. > [1] > http://src.opensolaris.org/source/xref/pkg/gate/src/modules/client/image.py#2596 > > This results in some later bits installed with then conflicts when > we try and install the 'entire' meta-cluster. You should be installing entire *first*. You're specifying the build 106 slim_install and getting it, but all the dependencies it brings in will be the latest. A "type=require" dependency brings in the latest available package, subject to current constraints, assuming it meets the minimum requirement specified by the fmri attribute of the action. Since you have no constraints on the system, it'll try to bring everything it installs up to the latest, so putting the constraint package down at the end isn't going to work. Danek
