Well, the "fix" mentioned didn't work. :) This is:
# uname -a
SunOS server2 5.10 Generic_Patch_118844-30 i86pc i386 i86pc
#
All patches suggested by smpatch have been installed. Including the patch with
the "fix".
# showrev -p | grep 119415-05
Patch: 119415-05 Obsoletes: Requires: Incompatibles: Packages:
SUNWgnome-a11y-libs, SUNWgnome-a11y-libs-share,
SUNWgnome-a11y-libs-devel-share, SUNWgnome-a11y-libs-devel
Yet:
# zonecfg -z zone7 info
zonepath: /export/zones/zone7
autoboot: true
pool:
net:
address: 66.91.129.189
physical: e1000g0
# zoneadm -z zone7 install
Preparing to install zone <zone7>.
Creating list of files to copy from the global zone.
Copying <131400> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <1053> packages on the zone.
Initialized <1053> packages on zone.
Zone <zone7> is initialized.
Installation of these packages generated warnings: <SUNWgnome-a11y-libs-share>
The file </export/zones/zone7/root/var/sadm/system/logs/install_log> contains a
log of the zone installation.
#
Thus, still no working Studio 11 install inside the zone. Any other ideas? This
is a bit frustrating, I can't complete migration of services until I can
compile the ones I need. ;)
Thanks,
David
----- Original Message -----
From: [EMAIL PROTECTED]
Date: Tuesday, April 18, 2006 10:55 am
Subject: Re: [zones-discuss] studio 11/zones/weird issue with java
> > http://corenode.com/~ormandj/files/install_log
>
> Thanks, that confirmed my suspicion. Although it's a GNOME package
> that is producing an error, it ends up causing a later Java error
> downstream. The relevant bug is
>
> 6340516 wholeroot zone install generated warnings for
> SUNWgnome-a11y-libs-share
>
> It's fixed in revent Solaris Express builds as well as the upcoming
> Solaris Express release. It's also supposedly addressed in the
> following patches
>
> 119414-05 or later (sparc)
> 119415-05 or later (i386)
>
> although since the fix is to correct SUNWgnome-a11y-libs-share's
> dependencies, I'm not sure if this is fixed by applying the patch to
> the global zone.
>
> dsc
>
_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org
