Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 05/11] gperf: upgrade to 3.1
Date: Mon, 24 Jul 2017 17:28:12 +0300	[thread overview]
Message-ID: <20170724142818.44403-5-alexander.kanavin@linux.intel.com> (raw)
In-Reply-To: <20170724142818.44403-1-alexander.kanavin@linux.intel.com>

Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
---
 meta/recipes-extended/gperf/gperf_3.0.4.bb | 5 -----
 meta/recipes-extended/gperf/gperf_3.1.bb   | 5 +++++
 2 files changed, 5 insertions(+), 5 deletions(-)
 delete mode 100644 meta/recipes-extended/gperf/gperf_3.0.4.bb
 create mode 100644 meta/recipes-extended/gperf/gperf_3.1.bb

diff --git a/meta/recipes-extended/gperf/gperf_3.0.4.bb b/meta/recipes-extended/gperf/gperf_3.0.4.bb
deleted file mode 100644
index 64003fc0bb7..00000000000
--- a/meta/recipes-extended/gperf/gperf_3.0.4.bb
+++ /dev/null
@@ -1,5 +0,0 @@
-require gperf.inc
-
-
-SRC_URI[md5sum] = "c1f1db32fb6598d6a93e6e88796a8632"
-SRC_URI[sha256sum] = "767112a204407e62dbc3106647cf839ed544f3cf5d0f0523aaa2508623aad63e"
diff --git a/meta/recipes-extended/gperf/gperf_3.1.bb b/meta/recipes-extended/gperf/gperf_3.1.bb
new file mode 100644
index 00000000000..942820b91d5
--- /dev/null
+++ b/meta/recipes-extended/gperf/gperf_3.1.bb
@@ -0,0 +1,5 @@
+require gperf.inc
+
+
+SRC_URI[md5sum] = "9e251c0a618ad0824b51117d5d9db87e"
+SRC_URI[sha256sum] = "588546b945bba4b70b6a3a616e80b4ab466e3f33024a352fc2198112cdbb3ae2"
-- 
2.13.2



  parent reply	other threads:[~2017-07-24 14:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24 14:28 [PATCH 01/11] icu: update to 59.1 Alexander Kanavin
2017-07-24 14:28 ` [PATCH 02/11] btrfs-tools: upgrade to 4.11.1 Alexander Kanavin
2017-07-24 14:28 ` [PATCH 03/11] bash-completion: upgrade to 2.7 Alexander Kanavin
2017-07-24 14:28 ` [PATCH 04/11] epiphany: upgrade to 3.24.3 Alexander Kanavin
2017-07-24 14:28 ` Alexander Kanavin [this message]
2017-07-25 13:12   ` [PATCH 05/11] gperf: upgrade to 3.1 Burton, Ross
2017-07-25 13:53     ` Khem Raj
2017-07-28 14:50       ` Burton, Ross
2017-07-31  9:35         ` Alexander Kanavin
2017-07-31  9:43           ` Richard Purdie
2017-07-31  9:53             ` Alexander Kanavin
2017-07-31 10:18               ` Alexander Kanavin
2017-07-31 14:55                 ` Burton, Ross
2017-07-31 14:58                   ` Khem Raj
2017-07-31 15:03             ` Burton, Ross
2017-07-24 14:28 ` [PATCH 06/11] vala: upgrade to 0.36.4 Alexander Kanavin
2017-07-24 14:28 ` [PATCH 07/11] eudev: update to 3.2.2 Alexander Kanavin
2017-07-24 14:28 ` [PATCH 08/11] mpg123: update to 1.25.4 Alexander Kanavin
2017-07-24 14:28 ` [PATCH 09/11] oprofile: fix upstream version check Alexander Kanavin
2017-07-24 14:28 ` [PATCH 10/11] webkitgtk: update to 2.16.6 Alexander Kanavin
2017-07-24 14:28 ` [PATCH 11/11] valgrind: fix upstream version check 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=20170724142818.44403-5-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