Hi Tim, Thanks for the replay. I found following two cases do not work 1. Copy the p5p file to global zone and local zone but their paths are different on global zone and local zone. Set the publisher on global zone and local zone with #pkg set-publisher -g <path> <publisher> command with corresponding path.Say /tmp on global zone and / on local zone. in this case package install fails with following error ---------------------------------------------- A 'sync-linked' operation failed for child 'zone:testzone' with an unexpected return value of 1 and the following error message: pkg: 0/1 catalogs successfully updated:
Unable to contact valid package repository Encountered the following error(s): Unable to contact any configured publishers. This is likely a network configuration problem. file protocol error: code: 22 reason: The path '/Mypkg.p5p' does not contain a valid package repository. Repository URL: 'file:///Mypkg.p5p'. ---------------------------------------------- 2. if we try to set the publisher on global zone, with pkg set-publisher -p option, then the SMF service /application/pkg/system-repository in global zone will go to maintenance state and thus do not allow to set a publisher in local zone. But when I repeat the step #1 with my p5p package with same path say /tmp on global and local zone (and with -g option to set-publisher), package install works fine on both global zone and local zone. is this intentional? The pkgrepo out for global and local zones are same as below # pkgrepo -s /tmp/Mypkg.p5p list PUBLISHER NAME O VERSION testpub Mypkg 1.0.100.0,5.11:20130112T013032Z On Wed, Mar 20, 2013 at 5:32 PM, <[email protected]>wrote: > Send pkg-discuss mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://mail.opensolaris.org/mailman/listinfo/pkg-discuss > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of pkg-discuss digest..." > > > Today's Topics: > > 1. Re: p5p package install with parent dependency within local > zones (Tim Foster) > 2. Code review reminder: pkg/update fix and sysrepo config > resiliency (Tim Foster) > 3. Re: Code review reminder: pkg/update fix and sysrepo config > resiliency (Erik Trauschke) > 4. Re: Code review reminder: pkg/update fix and sysrepo config > resiliency (Tim Foster) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 20 Mar 2013 09:03:32 +1300 > From: Tim Foster <[email protected]> > To: Sajith C R <[email protected]> > Cc: [email protected] > Subject: Re: [pkg-discuss] p5p package install with parent dependency > within local zones > Message-ID: <[email protected]> > Content-Type: text/plain; charset=UTF-8; format=flowed > > hi there, > > On 03/20/13 12:54 AM, Sajith C R wrote: > > 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? > > When you're doing the update, are you replacing the .p5p file with an > updated version in both the global and non-global zone? Otherwise, > that's the sort of error I'd expect you to run into. > > If that doesn't solve the problem, could you include more details as to > the specific error you're seeing, along with the output for 'pkgrepo -s > <p5p file> list' > > cheers, > tim > > > > ------------------------------ > > Message: 2 > Date: Wed, 20 Mar 2013 09:51:25 +1300 > From: Tim Foster <[email protected]> > To: pkg discuss <[email protected]> > Subject: [pkg-discuss] Code review reminder: pkg/update fix and > sysrepo config resiliency > Message-ID: <[email protected]> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hi there, > > Just a quick reminder that I've got two small fixes out for code review > at the moment, and was wondering if anyone had time to take a look? > > The webrevs are: > > > https://cr.opensolaris.org/action/browse/pkg/timf/sysrepo-resilient-config/sysrepo-resilient-config-webrev/ > > > https://cr.opensolaris.org/action/browse/pkg/timf/add-cronjob/add_cronjob-webrev > > The original mails to pkg-discuss were: > > Subject: Code review: making pkg.sysrepo more resilient in the face of > inaccessible file repos > (sent 02/26) > > Subject: Code review: add_cronjob failing after unclean shutdown > (sent 03/14) > > cheers, > tim > > > ------------------------------ > > Message: 3 > Date: Tue, 19 Mar 2013 15:07:56 -0700 > From: Erik Trauschke <[email protected]> > To: Tim Foster <[email protected]> > Cc: pkg discuss <[email protected]> > Subject: Re: [pkg-discuss] Code review reminder: pkg/update fix and > sysrepo config resiliency > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > > On 03/19/13 01:51 PM, Tim Foster wrote: > > Hi there, > > > > Just a quick reminder that I've got two small fixes out for code review > > at the moment, and was wondering if anyone had time to take a look? > > > > The webrevs are: > > > > > https://cr.opensolaris.org/action/browse/pkg/timf/sysrepo-resilient-config/sysrepo-resilient-config-webrev/ > > lgtm > > > > https://cr.opensolaris.org/action/browse/pkg/timf/add-cronjob/add_cronjob-webrev > > 154: nit: /contains/contain/ > > you're testing only for the existence of ${CMD} in the whole crontab. > How likely is it that this test might find something the user put in > there (or asked differently, how unique is ${CMD})? > > Erik > > > ------------------------------ > > Message: 4 > Date: Wed, 20 Mar 2013 11:37:09 +1300 > From: Tim Foster <[email protected]> > To: Erik Trauschke <[email protected]>, pkg discuss > <[email protected]> > Subject: Re: [pkg-discuss] Code review reminder: pkg/update fix and > sysrepo config resiliency > Message-ID: <[email protected]> > Content-Type: text/plain; charset=UTF-8; format=flowed > > On 03/20/13 11:07 AM, Erik Trauschke wrote: > >> > https://cr.opensolaris.org/action/browse/pkg/timf/sysrepo-resilient-config/sysrepo-resilient-config-webrev/ > > > > lgtm > > Thanks for taking a look! > > >> > https://cr.opensolaris.org/action/browse/pkg/timf/add-cronjob/add_cronjob-webrev > > > > 154: nit: /contains/contain/ > > Yep, I'll fix that. > > > you're testing only for the existence of ${CMD} in the whole crontab. > > How likely is it that this test might find something the user put in > > there (or asked differently, how unique is ${CMD})? > > Sure - I tried to address that in the comment at the top of > add_cronjob(). In this case, $CMD is unique in that it contains the > full SMF FMRI of the service we're looking to add/remove, eg. > > "/usr/sbin/svcadm refresh svc:/application/pkg/mirror:default" > > It specifically doesn't include the rest of the cron entry (namely the > cron schedule) because that can change as the user modifies SMF properties. > > For the consumers of this function, pkg/update and pkg/mirror, this is > enough I think. Yes, the pkg/update service would potentially clash if > we had more than one instance of the service running, since the command > it uses is: > > "/usr/lib/update-manager/update-refresh.sh" > > but that doesn't seem likely (and I hope we get to nuke pkg/update real > soon now anyway - its use of root's crontab is disturbing..) > > > Thanks for looking at these webrevs, much appreciated! > > cheers, > tim > > > ------------------------------ > > _______________________________________________ > pkg-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/pkg-discuss > > > End of pkg-discuss Digest, Vol 67, Issue 14 > ******************************************* > -- Thanks & regards, Sajith C R www.symantec.com Office: +912066157403 Mobile: +919881251259 _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
