From: "Wang Mingyu" <wangmy@cn.fujitsu.com>
To: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: [OE-core] [PATCH] valgrind: upgrade 3.16.0 -> 3.16.1
Date: Wed, 24 Jun 2020 09:21:59 +0000 [thread overview]
Message-ID: <1592990518861.84235@cn.fujitsu.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]
??Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com>
---
.../valgrind/{valgrind_3.16.0.bb => valgrind_3.16.1.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/valgrind/{valgrind_3.16.0.bb => valgrind_3.16.1.bb} (98%)
diff --git a/meta/recipes-devtools/valgrind/valgrind_3.16.0.bb b/meta/recipes-devtools/valgrind/valgrind_3.16.1.bb
similarity index 98%
rename from meta/recipes-devtools/valgrind/valgrind_3.16.0.bb
rename to meta/recipes-devtools/valgrind/valgrind_3.16.1.bb
index 4b6f5949dd..484a229a1a 100644
--- a/meta/recipes-devtools/valgrind/valgrind_3.16.0.bb
+++ b/meta/recipes-devtools/valgrind/valgrind_3.16.1.bb
@@ -41,8 +41,8 @@ SRC_URI = "https://sourceware.org/pub/valgrind/valgrind-${PV}.tar.bz2 \
file://0001-none-tests-fdleak_cmsg.stderr.exp-adjust-tmp-paths.patch \
file://0001-memcheck-tests-Fix-timerfd-syscall-test.patch \
"
-SRC_URI[md5sum] = "495b30af5e5ed62ebb9bb777ee19b27f"
-SRC_URI[sha256sum] = "582d5127ba56dfeaab4c6ced92a742b2921148e28a5d55055aedd8f75f1cf633"
+SRC_URI[md5sum] = "d1b153f1ab17cf1f311705e7a83ef589"
+SRC_URI[sha256sum] = "c91f3a2f7b02db0f3bc99479861656154d241d2fdb265614ba918cc6720a33ca"
UPSTREAM_CHECK_REGEX = "valgrind-(?P<pver>\d+(\.\d+)+)\.tar"
COMPATIBLE_HOST = '(i.86|x86_64|arm|aarch64|mips|powerpc|powerpc64).*-linux'
--
2.17.1
??
[-- Attachment #2: Type: text/html, Size: 2365 bytes --]
next reply other threads:[~2020-06-24 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 9:21 Wang Mingyu [this message]
2020-06-24 9:32 ` ✗ patchtest: failure for valgrind: upgrade 3.16.0 -> 3.16.1 Patchwork
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=1592990518861.84235@cn.fujitsu.com \
--to=wangmy@cn.fujitsu.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