jan damborsky stated: > Hi Sean, > > based on Danek's comment, I tried following steps on alternate root > (not with AI) - they seem to work: > > # pkg image-create -F -a opensolaris.org=http://ipkg.sfbay/dev /tmp/a > # pkg -R /tmp/a set-authority -m http://ipkg.czech:8000 opensolaris.org > # pkg -R /tmp/a install entire at 0.5.11-0.106 > # pkg -R /tmp/a install SUNWcsd > # pkg -R /tmp/a install SUNWcs > # pkg -R /tmp/a install slim_install at 0.1-0.106 > > The installation succeeded - image contains only 106 packages: > > # pkg -R /tmp/a list | grep -v 106 > NAME (AUTHORITY) VERSION STATE > UFIX > # pkg -R /tmp/a list | grep 106 | wc -l > 523 > #
Yup, we installed a few machines here with the 106 bits using this ordering for the packages: SUNWcsd SUNWcs entire SUNWj6rtx SUNWgroff SUNWgcc slim_install - then with the pgk version at the end, the machines installed fine and have only b106 bits, nothing later. Thanks folks. Sean. . > > It was not necessary to explicitly specify version for SUNWcsd, SUNWcs > packages, 106 were pulled into the image. I still had to specify version > for slim_install, otherwise I saw following failure: > > # pkg image-create -F -a opensolaris.org=http://ipkg.sfbay/dev /tmp/a > # pkg -R /tmp/a set-authority -m http://ipkg.czech:8000 opensolaris.org > # pkg -R /tmp/a install entire at 0.5.11-0.106 > # pkg -R /tmp/a install SUNWcsd > # pkg -R /tmp/a install SUNWcs > # pkg -R /tmp/a install slim_install > Creating Plan - pkg: pkg: the following package(s) > violated constraints: > Package pkg:/SUNWfcprt at 0.5.11,5.11-0.107 conflicts with constraint in > installed pkg:/entire: > Pkg SUNWfcprt: Optional min_version: 0.5.11,5.11-0.106 max > version: 0.5.11,5.11-0.106 defined by: pkg:/entire > > > Cheers, > Jan > > > On 02/19/09 17:13, Sean McGrath wrote: >> Sean McGrath stated: >> < jan damborsky stated: >> < > Hi Sean, >> < > >> < > >> < > On 02/18/09 13:46, Sean McGrath wrote: >> < >> The suituation: >> < >> Network boot a machine with AI image osol_0906-106a >> < >> Fine, creates the zpool, pulls the pkgs from repo, sets up grub etc.. >> < >> All nice. >> < >> >> < >> However the latest bits on the IPS repo are snv_107 based. >> < >> >> < >> So all the pkgs pulled with this 106 based AI image are snv_107 ones. >> < >> So we end up with a snv_107 based osol installed machine. >> < >> >> < >> The package version can be specified in the manifest like: >> < >> <ai_packages> >> < >> >> <package_name>slim_install at 0.1,5.11-0.106</package_name> < >> >> </ai_packages> >> < >> >> < >> (right ?) >> < > >> < > That is expected to work. But to be honest, I haven't tried, >> < > so please feel free to report possible issues there. >> < < Like this :) >> < < We've tried this and it still appears to install some later build >> pkgs. >> < < Suituation: using AI image osol_0906-106a and just want to install >> < the b106 packages - nothing newer or older. >> < < We pull the version of the pkg needed for the build we're installing >> < from the index/full_fmri_list file in the repo like: >> < < # 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> >> < < ok... >> < < But it seems that it still installs later build bits as from this >> error >> < - the error occured when the installer got to installing the >> < 'entire' package cluster. >> < < (from /var/svc/log/application-auto-installer:default.log): >> < ... >> < Indexing Packages ... Done >> < >> < 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. >> >> [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. >> >> cc'ing the pkg-discuss at opensolaris.org here too. >> >> Sean. >> . >> < < So it seems to have installed SUNWtls with b107 bits instead of b106. >> < and some others too: >> < < root at opensolaris:/a/var/pkg/index# grep 107: full_fmri_list >> >> < pkg:/SUNWpython-pyopenssl at 0.8,5.11-0.107:20090212T183536Z >> >> < pkg:/SUNWpython-mako at 0.2.2,5.11-0.107:20090212T183534Z >> >> < pkg:/SUNWpool at 0.5.11,5.11-0.107:20090212T183208Z >> >> < >> pkg:/SUNWcsl at 0.5.11,5.11-0.107:20090212T172317Z >> >> < pkg:/SUNWopenssl at 0.9.8,5.11-0.107:20090212T182806Z >> >> < pkg:/SUNWlibms at 0.5.11,5.11-0.107:20090212T181714Z >> >> < pkg:/SUNWlibsasl at 0.5.11,5.11-0.107:20090212T181735Z >> >> < >> pkg:/SUNWzlib at 1.2.3,5.11-0.107:20090212T185628Z >> >> < pkg:/SUNWlxml at 2.6.31,5.11-0.107:20090212T181817Z >> >> < pkg:/SUNWpr at 0.5.11,5.11-0.107:20090212T183504Z >> >> < pkg:/SUNWtls at 0.5.11,5.11-0.107:20090212T184617Z >> >> < >> pkg:/SUNWpython-cherrypy at 3.1.1,5.11-0.107:20090212T183528Z >> >> < root at opensolaris:/a/var/pkg/index# >> >> < < I've attached the ai_manifest.xml we use >> < < Regards, >> < Sean. >> < . >> >> >> < _______________________________________________ >> < caiman-discuss mailing list >> < caiman-discuss at opensolaris.org >> < http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >> >> > -- Sean. .
