On Fri 11 Nov 2011 at 08:41AM, Ian Collins wrote: > On 11/11/11 08:01 AM, Ian Collins wrote: > >On 11/11/11 02:39 AM, Mike Gerdts wrote: > >>On Thu 10 Nov 2011 at 08:32PM, Ian Collins wrote: > >>>On 10/10/11 07:20 PM, Edward Pilatowicz wrote: > >>>>by default packages that get installed into a zone are specified in the > >>>>default AI manifest used to install zones. you can find that manifest > >>>>here: > >>>> > >>>> /usr/share/auto_install/manifest/zone_default.xml > >>>I can't see that file (or the auto_instal directory) on any of my > >>>systems. Has it moved? > >>That file exists in Solaris 11 as part of the auto-install-common > >>package: > >> > >>$ pkg search /usr/share/auto_install/manifest/zone_default.xml > >>INDEX ACTION VALUE PACKAGE > >>path file usr/share/auto_install/manifest/zone_default.xml > >>pkg:/system/install/auto-install/auto-install-common@0.5.11-0.175.0.0.0.2.1482 > >> > >>With Solaris 11 Express, the list of packages was hard coded into > >>scripts under /usr/lib/brand/ipkg. What are you running? > >> > >Solaris 11 Express with the latest updates from the support repo. > > > >I'm getting an odd problem creating zones and I wanted to check the > >package list: > > > >Package State Update Phase 45/45 > >Image State Update Phase 2/2 > > Installing: Additional Packages (output follows) > >Creating Planpkg: 'SUNWbip' matches multiple packages > > SUNWbip > > compatibility/packages/SUNWbip > > > >ERROR: failed to install package > > > I removed SUNWbip from /usr/lib/brand/ipkg/pkgcreatezone and the > zone installed OK. I'll add the package in the zone later. > > Someone should have a look at a proper fix!
I believe that it is already fixed in pkg://solaris/system/zones/brand/ipkg@0.5.11,5.11-0.151.0.1.13:20111025T185520Z I think (but do not know) that you should be able to fix the problem you are seeing with: # pkg update pkg://solaris/system/zones/brand/ipkg Based on the dependencies in that package, it looks like that will also update pkg:/package/pkg to 0.5.11-0.151.0.1.13 as well. I'm sure there's a documented way that is a bit more customer friendly, but there's another way that is much more fun... Here begins a short tour through some of the bowels of packaging. Most of what I discuss below is not an interface. It may change at any time. First, I went to: http://pkg.oracle.com/solaris/release/ I clicked advanced search, entered "ipkg" (because I knew this was the tail end of the package name) in the search field, selected "Show all versions", then clicked the "Advanced Search" button. It showed me a list of packages, starting with: system/zones/brand/ipkg@0.5.11,5.11-0.151.0.1.13:20111025T185520Z which has a timestamp of October 25 (20111025). That looked promising. I clicked on the manifest and found the payload hash for pkgcreatezone from this line: file e95f13b8e67663890f420fc80814b62e473773e0 chash=51dc959c9d234ed9b2c33897a81c84bc86a77178 group=bin mode=0755 owner=root path=usr/lib/brand/ipkg/pkgcreatezone pkg.csize=6642 pkg.size=19838 That told me that I could find the new pkgcreatezone at http://pkg.oracle.com/solaris/release/file/1/e95f13b8e67663890f420fc80814b62e473773e0. Obvious, right? :) I saved that file, then used gzcat to see that all the package names are now fully qualified. Also, SUNWbip is no longer in the list. If SUNWbip were still needed, fully qualifying the name (e.g. pkg:/SUNWbip) would have done the trick. -- Mike Gerdts Solaris Core OS / Zones _______________________________________________ zones-discuss mailing list zones-discuss@opensolaris.org
