public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Valentin Popa <valentin.popa@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] gnutls: update to 3.2.13
Date: Wed, 30 Apr 2014 18:39:30 +0300	[thread overview]
Message-ID: <cover.1398871949.git.valentin.popa@intel.com> (raw)

Make sure you merge "wpa-supplicant: add libgcrypt as a dependencie"
and "nettle: add nettle to poky" before you test the new version of
gnutls.

The following changes since commit 17daa2ba6280304771c5fe52b94eb56f0c087490:

  bitbake: bb.utils, bb.codeparser: Add bb.utils.contains_any (2014-04-29 23:38:54 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib vpopa/gnutls_upgrade
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=vpopa/gnutls_upgrade

Valentin Popa (3):
  nettle: add nettle to poky
  gnutls: update to 3.2.13
  wpa-supplicant: add libgcrypt as a dependencie

 .../wpa-supplicant/wpa-supplicant.inc              |   2 +-
 meta/recipes-support/gnutls/gnutls.inc             |  28 +-
 .../gnutls/gnutls/25_updatedgdocfrommaster.diff    | 636 ---------------------
 .../CVE-2014-0092-corrected-return-codes.patch     | 106 ----
 ...14-1959-rejection-of-v1-intermediate-cert.patch |  33 --
 ..._MKDIR_P_warning_error_with_automake_1.12.patch |  51 --
 .../gnutls/gnutls/configure-fix.patch              |  65 ---
 .../correct_rpl_gettimeofday_signature.patch       |  36 +-
 .../gnutls/gnutls/fix-gettext-version.patch        |  46 --
 .../gnutls/gnutls/gnutls-openssl.patch             | 126 ----
 meta/recipes-support/gnutls/gnutls_2.12.23.bb      |  16 -
 meta/recipes-support/gnutls/gnutls_3.2.13.bb       |   7 +
 meta/recipes-support/nettle/nettle_2.7.1.bb        |  22 +
 13 files changed, 65 insertions(+), 1109 deletions(-)
 delete mode 100644 meta/recipes-support/gnutls/gnutls/25_updatedgdocfrommaster.diff
 delete mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2014-0092-corrected-return-codes.patch
 delete mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2014-1959-rejection-of-v1-intermediate-cert.patch
 delete mode 100644 meta/recipes-support/gnutls/gnutls/avoid_AM_PROG_MKDIR_P_warning_error_with_automake_1.12.patch
 delete mode 100644 meta/recipes-support/gnutls/gnutls/configure-fix.patch
 delete mode 100644 meta/recipes-support/gnutls/gnutls/fix-gettext-version.patch
 delete mode 100644 meta/recipes-support/gnutls/gnutls/gnutls-openssl.patch
 delete mode 100644 meta/recipes-support/gnutls/gnutls_2.12.23.bb
 create mode 100644 meta/recipes-support/gnutls/gnutls_3.2.13.bb
 create mode 100644 meta/recipes-support/nettle/nettle_2.7.1.bb

-- 
1.9.1



             reply	other threads:[~2014-04-30 15:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-30 15:39 Valentin Popa [this message]
2014-04-30 15:39 ` [PATCH 1/3] nettle: add nettle to poky Valentin Popa
2014-05-01 11:34   ` Paul Eggleton
2014-05-02 11:18     ` Valentin Popa
2014-05-01 14:29   ` Martin Jansa
2014-05-02 11:19   ` [PATCH 1/3] nettle: add nettle to oe-core Valentin Popa
2014-04-30 15:39 ` [PATCH 2/3] gnutls: update to 3.2.13 Valentin Popa
2014-04-30 15:39 ` [PATCH 3/3] wpa-supplicant: add libgcrypt as a dependencie Valentin Popa

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.1398871949.git.valentin.popa@intel.com \
    --to=valentin.popa@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