From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 3/4] libcheck: Upgrade to 0.9.14
Date: Wed, 30 Jul 2014 15:54:48 -0700 [thread overview]
Message-ID: <bb11ef806716bfab67cbe833bdd219b5119c3d18.1406760824.git.sgw@linux.intel.com> (raw)
In-Reply-To: <cover.1406760824.git.sgw@linux.intel.com>
In-Reply-To: <cover.1406760824.git.sgw@linux.intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
---
.../libcheck/{libcheck_0.9.13.bb => libcheck_0.9.14.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-support/libcheck/{libcheck_0.9.13.bb => libcheck_0.9.14.bb} (79%)
diff --git a/meta/recipes-support/libcheck/libcheck_0.9.13.bb b/meta/recipes-support/libcheck/libcheck_0.9.14.bb
similarity index 79%
rename from meta/recipes-support/libcheck/libcheck_0.9.13.bb
rename to meta/recipes-support/libcheck/libcheck_0.9.14.bb
index 8c063d4..2a69ff7 100644
--- a/meta/recipes-support/libcheck/libcheck_0.9.13.bb
+++ b/meta/recipes-support/libcheck/libcheck_0.9.14.bb
@@ -8,8 +8,8 @@ LIC_FILES_CHKSUM = "file://COPYING.LESSER;md5=2d5025d4aa3495befef8f17206a5b0a1"
SRC_URI = "${SOURCEFORGE_MIRROR}/check/check-${PV}.tar.gz \
"
-SRC_URI[md5sum] = "95530868f81a9496b2518fd2b713008a"
-SRC_URI[sha256sum] = "ca6589c34f9c60ffd4c3e198ce581e944a9f040ca9352ed54068dd61bebb5cb7"
+SRC_URI[md5sum] = "38263d115d784c17aa3b959ce94be8b8"
+SRC_URI[sha256sum] = "c272624645b1b738cf57fd5d81a3e4d9b722b99d6133ee3f3c4007d4d279840a"
S = "${WORKDIR}/check-${PV}"
--
1.8.3.1
next prev parent reply other threads:[~2014-07-30 22:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 22:54 [PATCH 0/4] Package Upgrades Saul Wold
2014-07-30 22:54 ` [PATCH 1/4] help2man-native: Upgrade to 1.46.1 Saul Wold
2014-07-30 22:54 ` [PATCH 2/4] lsbinitscripts: Upgrade to 9.55 Saul Wold
2014-07-30 22:54 ` Saul Wold [this message]
2014-07-30 22:54 ` [PATCH 4/4] libnl: Upgrade to 3.2.25 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=bb11ef806716bfab67cbe833bdd219b5119c3d18.1406760824.git.sgw@linux.intel.com \
--to=sgw@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