From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Reyna, David" <david.reyna@windriver.com>,
yocto <yocto@yoctoproject.org>,
Tracy Graydon <tracy.graydon@intel.com>
Cc: "CHAN, AARON CHUN YEW" <aaron.chun.yew.chan@intel.com>,
"otavio@ossystems.com.br" <otavio@ossystems.com.br>
Subject: Re: HELP: Release Candidate Build for yocto-2.4.3.rc2 now available.
Date: Tue, 29 May 2018 11:48:37 +0100 [thread overview]
Message-ID: <1527590917.16911.74.camel@linuxfoundation.org> (raw)
In-Reply-To: <5E53D14CE4667A45B9A06760DE5D13D0F38CA91E@ALA-MBD.corp.ad.wrs.com>
Hi David,
On Tue, 2018-05-29 at 03:36 +0000, Reyna, David wrote:
> I apologize for sending this patch for Toaster for Roco 2.4.3 very
> late. I have been focused on Sumo and I thought I had more time.
>
> The Toaster for Rocko is broken on HEAD. There are two patches that
> made it into master and Sumo, but missed Rocko.
>
> I have just now sent the missing patch set to "bitbake-dev". The
> first patch fixes an error that breaks the initialization of Toaster.
> The second patches fixes a change in behavior for Django that creates
> an extra thread that blocks Toaster from shutting down.
>
> Please accept these patches for Rocko. They are confined to Toaster
> and do not affect the rest of the release.
I've added the patches onto the rocko/2.36 branches but 2.4.3 is
already in QA now so we'd have to break process to add those in
potentially untested or go to an rc3.
At least they will be on the branch ready for update for anyone that
runs into the issue and we can release note. Lets see what else (if
anything) is found in rc2...
Cheers,
Richard
prev parent reply other threads:[~2018-05-29 10:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 3:36 HELP: Release Candidate Build for yocto-2.4.3.rc2 now available Reyna, David
2018-05-29 10:48 ` 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=1527590917.16911.74.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=aaron.chun.yew.chan@intel.com \
--cc=david.reyna@windriver.com \
--cc=otavio@ossystems.com.br \
--cc=tracy.graydon@intel.com \
--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.