From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] PULL: fixes to bug 961, 964
Date: Fri, 08 Apr 2011 06:17:23 -0700 [thread overview]
Message-ID: <1302268643.22904.121.camel@rex> (raw)
In-Reply-To: <1865303E0DED764181A9D882DEF65FB68A77210FCB@shsmsx502.ccr.corp.intel.com>
On Fri, 2011-04-08 at 18:04 +0800, Cui, Dexuan wrote:
> Dexuan Cui wrote:
> > From: Dexuan Cui <dexuan.cui@intel.com>
> >
> > [YOCTO #964]:
> > A recent commit 25a6e5f9(sstate: use only unique set of SSTATETASK)
> > breaks the ordered mapping between SSTATETASKS and SSTATETASKNAMES.
> > As a result, in sstate_cleanall, the line
> > taskname = tasks[namemap.index(name)]
> > gets an incorrect result, and "bitbake -c cleanall" doesn't really
> > remove the files populalted by do_populate_sysroot.
> >
> > BTW: the bernard branch doesn't need this fix since commit 25a6e5f9
> > wasn't pulled into it.
> >
> >
> >
> > [YOCTO #961]:
> > lsbsetup: Fix LIC_FILE_CHKSUM
> > We need to pull this fix asap since nightly's lsb builds have been
> > blocked by this for 2 days.
>
> Sorry, I didn't notice Saul had sent out a fix for this (bug #961). :-)
> Please ignore mine.
I've pulled the sstate patch into master, thanks!
Richard
prev parent reply other threads:[~2011-04-08 13:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 9:59 [PATCH 0/2] PULL: fixes to bug 961, 964 Dexuan Cui
2011-04-08 9:59 ` [PATCH 1/2] sstate: ensure an ordered mapping between SSTATETASKS and SSTATETASKNAMES Dexuan Cui
2011-04-11 0:40 ` Tian, Kevin
2011-04-08 9:59 ` [PATCH 2/2] lsbsetup: Fix LIC_FILE_CHKSUM Dexuan Cui
2011-04-08 10:04 ` [PATCH 0/2] PULL: fixes to bug 961, 964 Cui, Dexuan
2011-04-08 13:17 ` 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=1302268643.22904.121.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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.