Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [dylan][PATCH 00/15] Stable branch cherry-picks (cover letter only)
Date: Fri, 31 May 2013 16:10:38 +0100	[thread overview]
Message-ID: <cover.1370012780.git.paul.eggleton@linux.intel.com> (raw)

These are cherry-picks from master to be applied to the dylan branch for
inclusion in the next 1.4 stable release (1.4.1). They have been tested
on my build machine locally.

Please review this series for suitability for inclusion into the stable
branch.

The following changes since commit f24b4c3daeba43b352977fcdb807f1ed45c1c694:

  kern-tools: refresh and make dash compliant (2013-05-22 11:57:46 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib paule/dylan-next
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/dylan-next

Bogdan Marinescu (1):
  guile: added runtime dependency on glibc-gconv-iso8859-1

Bruce Ashfield (1):
  qemu*: restrict NFSD to linux-yocto only

Jackie Huang (1):
  guile: don't search for libreadline in host libdir

Jesse Zhang (2):
  dbus-glib: use BPN instead of PN
  initscripts: let status return 0 when proc is running well

Jessica Zhang (1):
  Make toolchain output name using SDK_VERSION instead of DISTRO_VERSION
    to be consistent [yocto #2342]

Jonathan Liu (3):
  systemd: fix ordering for machineid and run-postinsts services
  findutils: backport fixes for documentation build errors
  findutils: backport more fixes for documentation build errors

Ming Liu (1):
  dpkg-native: Fix native perl path

Nitin A Kamble (1):
  dropbear: a fix for hang in dropbearkey, built for x32

Paul Eggleton (1):
  python-smartpm: add gettext-native to DEPENDS

Richard Purdie (1):
  dpkg: Be deterministic about lzma dependency

Samuli Piippo (1):
  gdb-cross-canadian: use correct exec-prefix path for python

Xin Ouyang (1):
  qmake_base.bbclass: Add linux-gnun32-oe-g++ to QMAKESPEC

 meta/classes/populate_sdk_base.bbclass             |   2 +-
 meta/classes/qmake_base.bbclass                    |   2 +-
 meta/conf/machine/include/qemu.inc                 |   2 +-
 meta/recipes-core/dbus/dbus-glib.inc               |   8 +-
 .../0007-dropbear-fix-for-x32-abi.patch            | 140 +++++++++++++++++++++
 meta/recipes-core/dropbear/dropbear.inc            |   1 +
 .../initscripts/initscripts-1.0/functions          |   1 +
 .../systemd/systemd-compat-units/machineid.service |   2 +-
 .../systemd-compat-units/run-postinsts.service     |   2 +-
 meta/recipes-devtools/dpkg/dpkg.inc                |   4 +
 meta/recipes-devtools/gdb/gdb-cross-canadian.inc   |   2 +-
 meta/recipes-devtools/guile/guile_2.0.7.bb         |   4 +-
 .../python/python-smartpm_1.4.1.bb                 |   2 +-
 .../findutils-4.4.2/findutils_fix_doc.patch        |  84 +++++++++++++
 meta/recipes-extended/findutils/findutils_4.4.2.bb |   1 +
 15 files changed, 245 insertions(+), 12 deletions(-)
 create mode 100644 meta/recipes-core/dropbear/dropbear-2012.55/0007-dropbear-fix-for-x32-abi.patch
 create mode 100644 meta/recipes-extended/findutils/findutils-4.4.2/findutils_fix_doc.patch

-- 
1.8.1.2



                 reply	other threads:[~2013-05-31 15:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=cover.1370012780.git.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@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