From: Saul Wold <sgw@linux.intel.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [for-daisy] Pseudo backport breaks build in some hosts
Date: Wed, 05 Nov 2014 14:52:32 -0800 [thread overview]
Message-ID: <545AAA30.40604@linux.intel.com> (raw)
In-Reply-To: <CAP9ODKqZU0SpC_T_jYLExYKYLXQkLyv_7Vy7GW-9uA=_wBjLhQ@mail.gmail.com>
On 11/05/2014 12:34 PM, Otavio Salvador wrote:
> Hello,
>
> In clean hosts the pseudo build is broken. It seems to be lacking the
> attr dependency which has been added during the Dizzy development
> cycle but not included when doing the backport for Daisy; I suspect it
> has not been detected in Yocto Project AB because it should have attr
> headers available.
>
We actually just completed a full pass QA cycle on what was to be
1.6.2rc1, we found a couple of issues that are being address (like we
forgot to bump the actual Poky DISTRO_VERSION and the build-appliance
rev). Along with a couple more CVE patches that have come in. As you
point out it did go through a full AB, which has different Linux OS
setups. The fact that this was missed, I am not sure.
> We seem to need a better way to test backports as this is the second
> time backports has included regressions. I think we ought to have a
> daisy-next (and likely dizzy-next) branches with intended fixes for
> easy testing outside of Yocto Project AB and get wider exposure for
> different host setups.
>
So I have been pushing my changes to daisy-next prior to them being
merged into daisy itself. You are welcome to pull from it, test it and
report back, just beware that it can be rebased.
Sau!
> Best Regards,
>
next prev parent reply other threads:[~2014-11-05 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 20:34 [for-daisy] Pseudo backport breaks build in some hosts Otavio Salvador
2014-11-05 22:52 ` Saul Wold [this message]
2014-11-06 11:54 ` Otavio Salvador
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=545AAA30.40604@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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