All of lore.kernel.org
 help / color / mirror / Atom feed
From: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
To: yocto@yoctoproject.org
Subject: Re: Results from Yocto 1.0.1 Go/No-Go meeting: No-Go
Date: Thu, 19 May 2011 10:57:36 -0700	[thread overview]
Message-ID: <4DD55A10.3080800@intel.com> (raw)
In-Reply-To: <4DD55643.1090507@intel.com>



On 05/19/2011 10:41 AM, Saul Wold wrote:
> Investigation is complete.
>
> This issue is related to how libzypp constructs a header file in bitbake
> using PACKAGE_EXTRA_ARCHS. In 1.0.1 the PACKAGE_EXTRA_ARCHS was
> cumulative list defined in both crownbay*.conf and tune-atom.inc.  In
> 1.1 this was changed to just be set once in the tune-atom.inc.
>
> Because it was a cumulative list, it included x86 twice in 1.0.1 and
> only once and correctly 1.1.
>
> So the fix is in the crownbay BSP, and does not affect the core 1.0.1
> base as we currently have it.  This means no respin or re-test is
> required of the existing bit.
>
> ** Is this sufficient information to change to a "GO", pending the
> beagleboard testing at this point? **
>
> Sau!
>
>

I would like to just spin a nightly-external once the beagleboard patch gets in, to verify the fix. If the fix gets in 
today, I can have it done before our weekly 1.1-preM1 build.

---------------
Elizabeth Flanagan
Yocto Project
Release Engineer


  reply	other threads:[~2011-05-19 17:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-19 17:24 Results from Yocto 1.0.1 Go/No-Go meeting: No-Go Fleischer, Julie N
2011-05-19 17:41 ` Saul Wold
2011-05-19 17:57   ` Elizabeth Flanagan [this message]
2011-05-19 18:25     ` Fleischer, Julie N

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=4DD55A10.3080800@intel.com \
    --to=elizabeth.flanagan@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.