All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: [PATCH 0/1] check whether multiple versions of the same PN are due
Date: Mon, 2 Sep 2013 09:47:20 -0400	[thread overview]
Message-ID: <cover.1378129369.git.liezhi.yang@windriver.com> (raw)

This is used for fixing such a race issue:

$ bitbake make-3.81 make-3.82

There would be unexpected errors in the past, now, it will print the error
message and exit:

ERROR: Multiple .bb files are due to be built which each provide make (xxx)
 This usually means one provides something the other doesn't and should.
ERROR: Multiple versions of make are due to be built.

Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

// Robert

The following changes since commit c7994f83baa678a4670472e1f037bfc16cb1e3be:

  bitbake: runqueue: Fix scenequeue to pass file descriptors, not a float (2013-09-02 09:16:24 +0100)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib robert/same_pn
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=robert/same_pn

Robert Yang (1):
  runqueue.py: check whether multiple versions of the same PN are due to be built

 bitbake/lib/bb/runqueue.py |   12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

-- 
1.7.10.4



             reply	other threads:[~2013-09-02 13:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-02 13:47 Robert Yang [this message]
2013-09-02 13:47 ` [PATCH 1/1] runqueue.py: check whether multiple versions of the same PN are due to be built Robert Yang
2013-09-09 15:29   ` Richard Purdie

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=cover.1378129369.git.liezhi.yang@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=bitbake-devel@lists.openembedded.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.