On Tue, Mar 19, 2013 at 05:24:41PM +0530, Sajith C R wrote:
> Hi IPS team,
> I am facing following issue with p5p archive package install inside local
> zones on solaris 11.
> I use p5p format package to install my package on solaris 11 and the
> package contains following entries in the manifest to define parent
> dependency.
>
> depend type=parent fmri=feature/package/dependency/self
> variant.opensolaris.zone=nonglobal
>
> Prior to solaris 11 update, since the file based p5p publisher is not
> propagated inside a zone automatically, I had to install the p5p package
> inside local zones by copying the p5p file inside zone and then setting
> publisher inside zone which was working fine for me.
>
> with parent dependency mentioned, the package upgrades are not working with
> my p5p format packages.
> When publisher is set at global zone, IPS complain about version mismatch
> with local zone.
> If global zone is upgraded after detaching the local zone, later zone
> attach fails because of package version mismatch.
>
> I want to how to upgrade such packages on a pre-solaris 11 update1 setups?
>
> With solaris 11u1 onwards, this issue is not there as both global zone and
> local zones are updates together.
>
your options are:
- detach the zone, do the update, and then re-attach the zone in the new
post-u1 BE (this only works if you're upgrading to/past u1).
- extract the contenst of the p5p package and create a local http based
repo and configure the gz to use that.
- temporarly configure the p5p in the ngz from the gz. the trick here
is the *from the gz* part. ie, you'd do:
pkg -R /zonepath/root set-publisher -g /file_path.p5p <publisher>
the reason this should work is because when pkg update recurses into
the ngz it will attempt to lookup the p5p archive path relative to the
gz root.
ed
_______________________________________________
pkg-discuss mailing list
pkg-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
