Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org,
	richard.purdie@linuxfoundation.org
Subject: [PATCH 1/5] libidn: Upgrade to 1.30
Date: Mon, 18 May 2015 16:28:36 -0700	[thread overview]
Message-ID: <1431991720-19892-2-git-send-email-sgw@linux.intel.com> (raw)
In-Reply-To: <1431991720-19892-1-git-send-email-sgw@linux.intel.com>

LIC_CHKSUM updated because year was changed in those associated files.

Signed-off-by: Saul Wold <sgw@linux.intel.com>
---
 .../recipes-extended/libidn/{libidn_1.29.bb => libidn_1.30.bb} | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)
 rename meta/recipes-extended/libidn/{libidn_1.29.bb => libidn_1.30.bb} (75%)

diff --git a/meta/recipes-extended/libidn/libidn_1.29.bb b/meta/recipes-extended/libidn/libidn_1.30.bb
similarity index 75%
rename from meta/recipes-extended/libidn/libidn_1.29.bb
rename to meta/recipes-extended/libidn/libidn_1.30.bb
index 04b5344..7234747 100644
--- a/meta/recipes-extended/libidn/libidn_1.29.bb
+++ b/meta/recipes-extended/libidn/libidn_1.30.bb
@@ -3,13 +3,13 @@ DESCRIPTION = "Implementation of the Stringprep, Punycode and IDNA specification
 HOMEPAGE = "http://www.gnu.org/software/libidn/"
 SECTION = "libs"
 LICENSE = "(LGPLv2.1+ | LGPLv3) & GPLv3+"
-LIC_FILES_CHKSUM = "file://COPYING;md5=b35f8839295dd730a55f1a19ec086217 \
+LIC_FILES_CHKSUM = "file://COPYING;md5=df4be47940a91ee69556f5f71eed4aec \
                     file://COPYING.LESSERv2;md5=4fbd65380cdd255951079008b364516c \
                     file://COPYING.LESSERv3;md5=e6a600fd5e1d9cbde2d983680233ad02 \
                     file://COPYINGv2;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
                     file://COPYINGv3;md5=d32239bcb673463ab874e80d47fae504 \
-                    file://lib/idna.h;endline=21;md5=61a0e126c0c5552290d9bfa57e407dd6 \
-                    file://src/idn.c;endline=20;md5=3f55c28bede16bd7b1244be73067d195"
+                    file://lib/idna.h;endline=21;md5=7c0b3828d1b153663be9a04ad4f7975f \
+                    file://src/idn.c;endline=20;md5=f4235f2a2cb2b65786b2979fb3cf7fbf"
 
 inherit pkgconfig autotools gettext texinfo
 
@@ -19,8 +19,8 @@ SRC_URI = "${GNU_MIRROR}/libidn/${BPN}-${PV}.tar.gz \
            file://dont-depend-on-help2man.patch \
 "
 
-SRC_URI[md5sum] = "2b67bb507207af379f9461e1307dc84b"
-SRC_URI[sha256sum] = "fb82747dbbf9b36f703ed27293317d818d7e851d4f5773dedf3efa4db32a7c7c"
+SRC_URI[md5sum] = "b17edc8551cd31cc5f14c82a9dabf58e"
+SRC_URI[sha256sum] = "39b9fc94d74081c185757b12e0891ce5a22db55268e7d1bb24533ff4432eb053"
 
 # command tool is under GPLv3+, while libidn itself is under LGPLv2.1+ or LGPLv3
 # so package command into a separate package
-- 
2.1.0



  reply	other threads:[~2015-05-18 23:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18 23:28 [PATCH 0/5] Package Updates Saul Wold
2015-05-18 23:28 ` Saul Wold [this message]
2015-05-18 23:28 ` [PATCH 2/5] libksba: Upgrade to 1.3.3 Saul Wold
2015-05-18 23:28 ` [PATCH 3/5] libinitscripts: Upgrade to 9.63 Saul Wold
2015-05-18 23:28 ` [PATCH 4/5] msmtp: Upgrade to 1.6.2 Saul Wold
2015-05-18 23:28 ` [PATCH 5/5] liburcu: Upgrade to 0.8.7 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=1431991720-19892-2-git-send-email-sgw@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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