Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] Package Updates
Date: Tue,  2 Dec 2014 17:18:04 -0800	[thread overview]
Message-ID: <cover.1417552133.git.sgw@linux.intel.com> (raw)

The following changes since commit 68ddb28a68ceb59cd1ed322c16143827ce1ac712:

  distrodata_class: checkpkg make usage of latest_versionstring methods in bitbake fetcher (2014-11-28 13:59:52 +0000)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib sgw/updates
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=sgw/updates

Saul Wold (4):
  libaio: Upgrade to 3.110
  libgpg-error: Update to 1.17
  gnupg: Upgrade to 2.1.0
  valgrind: Upgrade to 3.10.0

 meta/conf/distro/include/security_flags.inc        |   1 +
 .../valgrind/remove-arm-variant-specific.patch     |  20 +-
 .../valgrind/remove-ppc-tests-failing-build.patch  |  26 +--
 .../valgrind/valgrind/valgrind-remove-rpath.patch  |  25 +++
 .../{valgrind_3.9.0.bb => valgrind_3.10.0.bb}      |   6 +-
 .../recipes-extended/libaio/libaio/00_arches.patch | 208 ++-------------------
 .../libaio/libaio/libaio-aarch64.patch             |  28 ---
 .../libaio/libaio/libaio_fix_for_mips64.patch      |  68 ++++---
 .../recipes-extended/libaio/libaio/toolchain.patch |  27 ---
 .../{libaio_0.3.109.bb => libaio_0.3.110.bb}       |   9 +-
 .../gnupg/gnupg/dirmngr-uses-libgpg-error.patch    |  16 ++
 meta/recipes-support/gnupg/gnupg/pkgconfig.patch   |  24 ++-
 .../use-pkgconfig-instead-of-npth-config.patch     |  72 +++++++
 .../gnupg/{gnupg_2.0.26.bb => gnupg_2.1.0.bb}      |  16 +-
 .../pkgconfig.patch                                |  67 ++++---
 .../{libgpg-error_1.12.bb => libgpg-error_1.17.bb} |  30 ++-
 16 files changed, 293 insertions(+), 350 deletions(-)
 create mode 100644 meta/recipes-devtools/valgrind/valgrind/valgrind-remove-rpath.patch
 rename meta/recipes-devtools/valgrind/{valgrind_3.9.0.bb => valgrind_3.10.0.bb} (94%)
 delete mode 100644 meta/recipes-extended/libaio/libaio/libaio-aarch64.patch
 delete mode 100644 meta/recipes-extended/libaio/libaio/toolchain.patch
 rename meta/recipes-extended/libaio/{libaio_0.3.109.bb => libaio_0.3.110.bb} (74%)
 create mode 100644 meta/recipes-support/gnupg/gnupg/dirmngr-uses-libgpg-error.patch
 create mode 100644 meta/recipes-support/gnupg/gnupg/use-pkgconfig-instead-of-npth-config.patch
 rename meta/recipes-support/gnupg/{gnupg_2.0.26.bb => gnupg_2.1.0.bb} (70%)
 rename meta/recipes-support/libgpg-error/{libgpg-error-1.12 => libgpg-error}/pkgconfig.patch (70%)
 rename meta/recipes-support/libgpg-error/{libgpg-error_1.12.bb => libgpg-error_1.17.bb} (40%)

-- 
1.8.3.1



             reply	other threads:[~2014-12-03  1:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03  1:18 Saul Wold [this message]
2014-12-03  1:18 ` [PATCH 1/4] libaio: Upgrade to 3.110 Saul Wold
2014-12-03 13:10   ` Burton, Ross
2014-12-03  1:18 ` [PATCH 2/4] libgpg-error: Update to 1.17 Saul Wold
2014-12-03 16:57   ` Burton, Ross
2014-12-03  1:18 ` [PATCH 3/4] gnupg: Upgrade to 2.1.0 Saul Wold
2014-12-03 16:25   ` Burton, Ross
2014-12-03  1:18 ` [PATCH 4/4] valgrind: Upgrade to 3.10.0 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=cover.1417552133.git.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