On Mon, Apr 16, 2018 at 10:39 AM, akuster808 <akuster...@gmail.com> wrote: > Hello, > > Was was running the yocto-check-layer sadly over the weekend and one for > the issues it note was: > > > ERROR: Nothing PROVIDES 'ostree' (but > /home/akuster/oss/maint/meta-virtualization/recipes-containers/cri-o/cri-o_git.bb > DEPENDS on or otherwise requires it). Close matches: > tree > ERROR: Required build target 'meta-world-pkgdata' has no buildable > providers. > Missing or unbuildable dependency chain was: ['meta-world-pkgdata', > 'cri-o', 'ostree'] > > > From what I can tell ostree is in meta-iot and a few other layers. Is > the intent to include one of the other layers as a requirement, include > your own copy of ostree, do a dynamic layer thing or something else?
One of the backends of cri-o is ostree, so yah, it is more of a custom configuration to put the outputs of that recipe into use for a given image. I should put more info into the README for the layer, and that you can get ostree from one of the other layers in the oe ecosystem. I ended up needing to make my own copy of the recipe into meta-overc, since the layers in question were making changes (or the recipe wasn't causing me other issues), and I need to revisit that. Bruce > > > Kind regards, > > Armin > > -- > _______________________________________________ > meta-virtualization mailing list > email@example.com > https://lists.yoctoproject.org/listinfo/meta-virtualization -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" -- _______________________________________________ meta-virtualization mailing list firstname.lastname@example.org https://lists.yoctoproject.org/listinfo/meta-virtualization