Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] cooker: fix traceback when using -b with skipped recipe
Date: Thu, 23 Aug 2012 08:50:22 +0100	[thread overview]
Message-ID: <1345708222.12043.0.camel@ted> (raw)
In-Reply-To: <1345648478-2678-1-git-send-email-paul.eggleton@linux.intel.com>

On Wed, 2012-08-22 at 16:14 +0100, Paul Eggleton wrote:
> If a recipe is skipped during parsing for whatever reason, check and
> report this as an error rather than trying to use the data that is sent
> back and failing.
> 
> Fixes [YOCTO #2976].
> 
> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> ---
>  bitbake/lib/bb/cooker.py |    4 ++++
>  1 file changed, 4 insertions(+)

Merged to master, thanks.

Richard




      reply	other threads:[~2012-08-23  8:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22 15:14 [PATCH] cooker: fix traceback when using -b with skipped recipe Paul Eggleton
2012-08-23  7:50 ` Richard Purdie [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=1345708222.12043.0.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox