From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 03/15] iso-codes: upgrade to 3.69
Date: Mon, 29 Aug 2016 17:30:10 +0300 [thread overview]
Message-ID: <fd2ffdd9e66bb216c352a03af18882d0ecde14d5.1472480768.git.alexander.kanavin@linux.intel.com> (raw)
In-Reply-To: <cover.1472480768.git.alexander.kanavin@linux.intel.com>
In-Reply-To: <cover.1472480768.git.alexander.kanavin@linux.intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
---
.../iso-codes/{iso-codes_3.68.bb => iso-codes_3.69.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-support/iso-codes/{iso-codes_3.68.bb => iso-codes_3.69.bb} (76%)
diff --git a/meta/recipes-support/iso-codes/iso-codes_3.68.bb b/meta/recipes-support/iso-codes/iso-codes_3.69.bb
similarity index 76%
rename from meta/recipes-support/iso-codes/iso-codes_3.68.bb
rename to meta/recipes-support/iso-codes/iso-codes_3.69.bb
index f8bcc48..105949f 100644
--- a/meta/recipes-support/iso-codes/iso-codes_3.68.bb
+++ b/meta/recipes-support/iso-codes/iso-codes_3.69.bb
@@ -3,8 +3,8 @@ LICENSE = "LGPLv2.1"
LIC_FILES_CHKSUM = "file://COPYING;md5=4fbd65380cdd255951079008b364516c"
SRC_URI = "https://pkg-isocodes.alioth.debian.org/downloads/iso-codes-${PV}.tar.xz"
-SRC_URI[md5sum] = "a5ce7d78b80f6d29150883d892f2e185"
-SRC_URI[sha256sum] = "5881cf7caa5adfffb14ade99138949324c28a277babe8d07dafbff521acef9d1"
+SRC_URI[md5sum] = "33ed5ea7eed84a7609f041c838fc96d7"
+SRC_URI[sha256sum] = "3f285d3c13f4dccfbdb9e432f172403ac1a54ab432616f10556eb18c23a1c0b2"
# inherit gettext cannot be used, because it adds gettext-native to BASEDEPENDS which
# are inhibited by allarch
--
2.9.3
next prev parent reply other threads:[~2016-08-29 14:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 14:30 [PATCH 00/15] Version updates and webkitgtk build race fix Alexander Kanavin
2016-08-29 14:30 ` [PATCH 01/15] libwebp: upgrade to 0.5.1 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 02/15] btrfs-tools: update to 4.7.1 Alexander Kanavin
2016-08-29 14:30 ` Alexander Kanavin [this message]
2016-08-29 14:30 ` [PATCH 04/15] bash-completion: update to 2.4 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 05/15] bdwgc: update to 7.6.0 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 06/15] ffmpeg: update to 3.1.2 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 07/15] gobject-introspection: odd versions are development snapshots Alexander Kanavin
2016-08-29 14:30 ` [PATCH 08/15] gnutls: update to 3.5.3 Alexander Kanavin
2016-08-30 22:43 ` Richard Purdie
2016-08-31 8:50 ` [PATCHv2 " Jussi Kukkonen
2016-08-29 14:30 ` [PATCH 09/15] kexec-tools: update to 2.0.13 Alexander Kanavin
2016-08-31 6:57 ` Robert Yang
2016-08-29 14:30 ` [PATCH 10/15] lighttpd: update to 1.4.41 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 11/15] mpg123: update to 1.23.6 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 12/15] nss: update to 3.25 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 13/15] asciidoc: fix upstream version check Alexander Kanavin
2016-08-29 14:30 ` [PATCH 14/15] webkitgtk: upgrade to 2.12.4 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 15/15] webkitgtk: fix racy double build of WebKit2-4.0.gir Alexander Kanavin
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=fd2ffdd9e66bb216c352a03af18882d0ecde14d5.1472480768.git.alexander.kanavin@linux.intel.com \
--to=alexander.kanavin@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