From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: akuster808 <akuster808@gmail.com>
Cc: meta-virtualization@yoctoproject.org
Subject: Re: Intent of cri-o recipe
Date: Mon, 16 Apr 2018 15:36:46 -0400 [thread overview]
Message-ID: <CADkTA4OBw8Cyvw=2WqOzQX0uratTtCpR+WXvmK=7ob97r+qfmQ@mail.gmail.com> (raw)
In-Reply-To: <4a9c58ef-c00c-c113-ccfd-11e823c593f6@gmail.com>
On Mon, Apr 16, 2018 at 10:39 AM, akuster808 <akuster808@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
> meta-virtualization@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-virtualization
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
prev parent reply other threads:[~2018-04-16 19:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 14:39 Intent of cri-o recipe akuster808
2018-04-16 19:36 ` Bruce Ashfield [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADkTA4OBw8Cyvw=2WqOzQX0uratTtCpR+WXvmK=7ob97r+qfmQ@mail.gmail.com' \
--to=bruce.ashfield@gmail.com \
--cc=akuster808@gmail.com \
--cc=meta-virtualization@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.