On Wed, Jan 27, 2010 at 07:31:32PM -0600, Shawn Walker wrote: > On 01/27/10 07:14 PM, [email protected] wrote: > >On Wed, Jan 27, 2010 at 06:50:46PM -0600, Shawn Walker wrote: > >>Actually, in 14201, get_manifest() was called as a result of a > >>lazy-load trigger from get_pkg_list() as the packagemanager was > >>building its list of packages. Because the package was from a v0 > >>repository, the lazy-loader got triggered. > > > >Sorry I missed that. I apologize for my ignorance, but in this > >situation are we building the catalog for the first time? If so > >is it the merged catalog? > > No, as far as I can tell, the merged catalog has already been built. > The client (packagemanager) is just asking for a list of packages. > For some reason, there is a package in the merged catalog that is > not installed, but isn't present in the publisher's catalog, which > causes the resulting error. > > This could be related to bug 14013 which I fixed just recently in > the gate. It would certainly explain how a package that is no > longer available, and not installed (I'm guessing), could have been > in the merged catalog and triggered a lazy-load. > > To clarify, whenever the image catalog is built, packages from a v0 > repository do *not* get their manifest data merged into the image > catalog. Instead, every time a caller asks for action data from the > merged catalog for a package from a v0 repository, it lazy-loads it > from a manifest.
Thanks for the clarification. Would it make sense to put a sanity check in the lazy-load where we check that the fmri is in the catalog, or is that effectively what you asked me to file a bug for? Thanks, -j _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
