All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe MacDonald <Joe_MacDonald@mentor.com>
To: Pello Heriz <pello.heriz@alumni.mondragon.edu>
Cc: yocto@yoctoproject.org, meta-virtualization@yoctoproject.org
Subject: Re: No recipes available for meta-selinux and meta-virtualization layers
Date: Mon, 10 Apr 2017 09:05:06 -0400	[thread overview]
Message-ID: <20170410130505.GA11174@mentor.com> (raw)
In-Reply-To: <CAFL6qn4COY_d-uRBe-ausjbW+7MOUkU6gU8kkqkHj_gokxxmEw@mail.gmail.com>

Hi Pello,

[No recipes available for meta-selinux and meta-virtualization layers] On 17.04.10 (Mon 09:59) Pello Heriz wrote:

> Hi,
> 
> I have tried to build a core-image-minimal image with master branch of
> Yocto and I have added the meta-virtualization layer and it's
> dependency layers in order to have virtualization functionalities
> enabled when creating the image.
> 
> The problem is that the bitbake execution fails due to there are
> missing some recipes for meta-selinux and meta-virtualization layers.
> This is the message that I can see in the terminal when it fails the
> execution:

Yeah, Mark and I have discussed a few times that we're sorely out of
date in meta-selinux right now.  At different times we've each said we
were going to do an update to the layer, but frankly we're both pretty
swamped and there's a couple of infrastructural issues too that we've
both been hoping to resolve "pretty soon".

That said, as a stop-gap, you could try checking out the updated
master-next branch in meta-selinux.  Just a few minutes ago I pushed
some changes that may resolve some of those issues for you.

Also, just FYI, I don't typically test anything in meta-selinux outside
of the combination with DISTRO=poky-selinux or oe-selinux and a
core-image-selinux, so you may encounter issues I haven't seen when
building something else.  But we're happy to take patches for those
additional cases, just know that you may be blazing your own trail.

-J.

> 
> pello@pello-VirtualBox:/opt/yocto_GE/yocto_master_xen/poky/build$ bitbake
> core-image-minimal
> Parsing recipes: 100% |########################################################
> ##########################| Time: 0:09:00
> Parsing of 1981 .bb files complete (0 cached, 1981 parsed). 2752 targets, 204
> skipped, 0 masked, 0 errors.
> ERROR: No recipes available for:
>   /opt/yocto_GE/yocto_master_xen/poky/meta-selinux/recipes-devtools/rpm/
> rpm_5.4.16.bbappend
>   /opt/yocto_GE/yocto_master_xen/poky/meta-selinux/recipes-extended/findutils/
> findutils_4.2.31.bbappend
>   /opt/yocto_GE/yocto_master_xen/poky/meta-virtualization/recipes-kernel/linux/
> linux-yocto_4.8.bbappend
> 
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
> 
> 
> How can be solved this error? Are you planned to update some patch for solving
> this issue?
> 
> Looking forward to your answer,
> Best regards,
> Pello

-- 
-Joe MacDonald.
:wq


  reply	other threads:[~2017-04-10 13:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-10  7:59 No recipes available for meta-selinux and meta-virtualization layers Pello Heriz
2017-04-10 13:05 ` Joe MacDonald [this message]
2017-04-10 19:06 ` [meta-virtualization] " Mark Asselstine
2017-04-10 19:06   ` Mark Asselstine

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=20170410130505.GA11174@mentor.com \
    --to=joe_macdonald@mentor.com \
    --cc=meta-virtualization@yoctoproject.org \
    --cc=pello.heriz@alumni.mondragon.edu \
    --cc=yocto@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.