All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: Release-2011.03: Let the testing continue again!
Date: Fri, 25 Feb 2011 08:01:27 -0700	[thread overview]
Message-ID: <4D67C447.9050906@mentor.com> (raw)
In-Reply-To: <4D66E88B.6040506@mentor.com>

On 02/24/2011 04:23 PM, Tom Rini wrote:
> Hey all,
>
> I've updated the testing-release-2011.03 branch exist now and we're
> ready for more testing. As a reminder, please update the table on
> http://wiki.openembedded.org/index.php?title=Release-2011.03 with your
> results and the githash you're on.
>
> This go-around should be much less bumpy as we've both fixed a number of
> RPATH issues and made the error non-fatal. I've also pushed a small
> number of fixes for issues I hit in my builder but once again need to
> add one more thing locally to confirm or rule out an occasional bug (the
> config.sub failure I reported earlier in testing out the cross.bbclass
> patch for RPATH stuff).
>
> If all goes well, I plan to make a temporary branch Tuesday, add in (and
> then revert from master at Khem's request)
> http://patches.openembedded.org/patch/256/ since it is needed for
> SHR/shr-image to work. Get one last go-round and then call it a release.
>
> Thanks again all!

Given the libnl2 breakage I plan to update the branch again today around 
2pm (-0700) to again current to make sure folks running things over the 
weekend don't hit that problem.

-- 
Tom Rini
Mentor Graphics Corporation



  parent reply	other threads:[~2011-02-25 15:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24 23:23 Release-2011.03: Let the testing continue again! Tom Rini
2011-02-25  7:14 ` Andreas Mueller
2011-02-25 15:00   ` Tom Rini
2011-02-25 15:01 ` Tom Rini [this message]
2011-02-25 15:13   ` Petr Štetiar

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=4D67C447.9050906@mentor.com \
    --to=tom_rini@mentor.com \
    --cc=openembedded-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.