Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] Priorty patches for 1.6.2
Date: Fri, 31 Oct 2014 14:54:45 -0700	[thread overview]
Message-ID: <1414792488-4932-1-git-send-email-sgw@linux.intel.com> (raw)

The following patches address QA issues with the release, while we don't normally
update recipes, the pseudo update is needed because of the 64bit XFS inode isses
encountered on the Auto builder creating the images.

There is one pending pacth on the Poky list for updating the DISTRO_VERSION, along 
Scott's Documentation branch has 1.6.2 updates. I would also like to include the 
CVE for curl that's pending, but has not hit master yet.

Finally once curl is in also a build-appliance update will be needed on Poky Branch.

Thanks
	Sau!

Alejandro Hernandez (1):
  ltp: Added zip-native as a DEPENDS

Peter Seebach (1):
  pseudo*.bb: update to pseudo 1.6.2

Richard Purdie (1):
  yocto-bsp: Update qemu inclusion lists

 meta/recipes-devtools/pseudo/pseudo_1.5.1.bb              | 15 ---------------
 meta/recipes-devtools/pseudo/pseudo_1.6.2.bb              | 10 ++++++++++
 meta/recipes-devtools/pseudo/pseudo_git.bb                |  4 ++--
 meta/recipes-extended/ltp/ltp_20140115.bb                 |  2 +-
 .../target/arch/qemu/conf/machine/{{=machine}}.conf       |  5 +++--
 5 files changed, 16 insertions(+), 20 deletions(-)
 delete mode 100644 meta/recipes-devtools/pseudo/pseudo_1.5.1.bb
 create mode 100644 meta/recipes-devtools/pseudo/pseudo_1.6.2.bb

-- 
1.8.3.1



             reply	other threads:[~2014-10-31 21:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31 21:54 Saul Wold [this message]
2014-10-31 21:54 ` [PATCH 1/3] pseudo*.bb: update to pseudo 1.6.2 Saul Wold
2014-10-31 21:54 ` [PATCH 2/3] yocto-bsp: Update qemu inclusion lists Saul Wold
2014-10-31 21:54 ` [PATCH 3/3] ltp: Added zip-native as a DEPENDS Saul Wold

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=1414792488-4932-1-git-send-email-sgw@linux.intel.com \
    --to=sgw@linux.intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox