On 07/06/2012 13:08, Liam Merwick wrote:
Hi Folks,
The 'ldomsmanager' package is only intended to be installed in a global zone
(and the value of
variant.opensolaris.zone is set to 'global' in the package manifest). Why would
the 'pkg contents'
output on s11u1_18 vary depending on the type of zone it was run on? Is this
related to a new
feature of system repositories/proxies (which I'll admit I've paid little
attention to). Or is there
something else that now needs to be specified in a manifest for s11u1 to block
installation in a NGZ?
I subsequently got access to the broken Zone in ON-PIT. 'entire' wasn't installed and some random
pre 11.0 'ldomsmanager' (without the zone variant fixes) was installed on s11u1_18 which explains
the problem.
Sorry about the noise.
Regards,
Liam
Regards,
Liam
------ output from s11u1_18 (built by ON-PIT) ----------------
root@thumbnut:~# pkg contents -m ldomsmanager | grep global
set name=variant.opensolaris.zone value=global
root@thumbnut:~# zlogin thumbnut-z3
[Connected to zone 'thumbnut-z3' pts/1]
Oracle Corporation SunOS 5.11 11.1 Jun. 05, 2012
SunOS Internal Development: gk 2012-Jun-05 [s11u1_18]
root@thumbnut-z3:~# pkg contents -m ldomsmanager | grep global
set name=variant.opensolaris.zone value=global value=nonglobal
variant.arch=sparc
------ output from a Zone I created on the latest SRU ----------------
root@testzone:~# pkg contents -r -m ldomsmanager | grep zone
set name=variant.opensolaris.zone value=global
root@testzone:~# pkg list -H entire
entire 0.5.11-0.175.0.8.0.3.0 i--
(Trying to install ldomsmanager fail as expected)
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
