From: "Wang Mingyu" <wangmy@cn.fujitsu.com>
To: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: [OE-core] [PATCH] man-pages: upgrade 5.06 -> 5.07
Date: Wed, 24 Jun 2020 09:22:00 +0000 [thread overview]
Message-ID: <1592990520040.51768@cn.fujitsu.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1387 bytes --]
??file README update.
Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com>
---
.../man-pages/{man-pages_5.06.bb => man-pages_5.07.bb} | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
rename meta/recipes-extended/man-pages/{man-pages_5.06.bb => man-pages_5.07.bb} (81%)
diff --git a/meta/recipes-extended/man-pages/man-pages_5.06.bb b/meta/recipes-extended/man-pages/man-pages_5.07.bb
similarity index 81%
rename from meta/recipes-extended/man-pages/man-pages_5.06.bb
rename to meta/recipes-extended/man-pages/man-pages_5.07.bb
index 0d632e6170..04d0597b3d 100644
--- a/meta/recipes-extended/man-pages/man-pages_5.06.bb
+++ b/meta/recipes-extended/man-pages/man-pages_5.07.bb
@@ -4,11 +4,11 @@ SECTION = "console/utils"
HOMEPAGE = "http://www.kernel.org/pub/linux/docs/man-pages"
LICENSE = "GPLv2+"
-LIC_FILES_CHKSUM = "file://README;md5=794f701617cc03fe50c53257660d8ec4"
+LIC_FILES_CHKSUM = "file://README;md5=207f70f56526417514ac46b6680e314f"
SRC_URI = "${KERNELORG_MIRROR}/linux/docs/${BPN}/${BP}.tar.gz"
-SRC_URI[md5sum] = "ebddb52ea013c160f07fd0a4a7e9266d"
-SRC_URI[sha256sum] = "da4e939c624bec4bab8ca1702e5f54bbc70505090d90967fd5e12bc1453f19b0"
+SRC_URI[md5sum] = "193d9223e9c6dbe1d928eaaecc1f68db"
+SRC_URI[sha256sum] = "5ba58d7b2b9a8929903b1cf791ed4edf72ab225678d5ea0a6b80dc090080ac33"
inherit manpages
--
2.17.1
?
[-- Attachment #2: Type: text/html, Size: 2380 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:22 Wang Mingyu [this message]
2020-06-24 9:32 ` ✗ patchtest: failure for man-pages: upgrade 5.06 -> 5.07 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=1592990520040.51768@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