Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Maxin B. John" <maxin.john@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/2] libunistring: upgrade to version 0.9.6
Date: Thu, 19 Nov 2015 19:02:55 +0200	[thread overview]
Message-ID: <1447952575-26935-2-git-send-email-maxin.john@intel.com> (raw)
In-Reply-To: <1447952575-26935-1-git-send-email-maxin.john@intel.com>

0.9.5 -> 0.9.6

Signed-off-by: Maxin B. John <maxin.john@intel.com>
---
 .../libunistring/{libunistring_0.9.5.bb => libunistring_0.9.6.bb}     | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-support/libunistring/{libunistring_0.9.5.bb => libunistring_0.9.6.bb} (90%)

diff --git a/meta/recipes-support/libunistring/libunistring_0.9.5.bb b/meta/recipes-support/libunistring/libunistring_0.9.6.bb
similarity index 90%
rename from meta/recipes-support/libunistring/libunistring_0.9.5.bb
rename to meta/recipes-support/libunistring/libunistring_0.9.6.bb
index 45cf633..bb70122 100644
--- a/meta/recipes-support/libunistring/libunistring_0.9.5.bb
+++ b/meta/recipes-support/libunistring/libunistring_0.9.6.bb
@@ -21,8 +21,8 @@ SRC_URI = "${GNU_MIRROR}/libunistring/libunistring-${PV}.tar.gz \
            file://iconv-m4-remove-the-test-to-convert-euc-jp.patch \
            file://0001-Unset-need_charset_alias-when-building-for-musl.patch \
 "
-SRC_URI[md5sum] = "1a705bcdcb83799d544137617b377cfd"
-SRC_URI[sha256sum] = "1a8c0772467850bef7197318a95f44abbb678ea83cbf119a3500cc7848276a17"
+SRC_URI[md5sum] = "dfae4ff5583649ed24d8f368f1d0543b"
+SRC_URI[sha256sum] = "9625eec2507f4789ebb6fc48ebda98be0e0168979a2f68aa8b680bf8eeabbd47"
 
 inherit autotools texinfo
 BBCLASSEXTEND = "native nativesdk"
-- 
2.4.0



      reply	other threads:[~2015-11-19 17:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19 17:02 [PATCH 1/2] libtasn1: upgrade to 4.7 Maxin B. John
2015-11-19 17:02 ` Maxin B. John [this message]

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=1447952575-26935-2-git-send-email-maxin.john@intel.com \
    --to=maxin.john@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