From: "Wang Mingyu" <wangmy@cn.fujitsu.com>
To: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: [OE-core] [PATCH] man-db: upgrade 2.9.2 -> 2.9.3
Date: Wed, 24 Jun 2020 09:21:56 +0000 [thread overview]
Message-ID: <1592990515965.50599@cn.fujitsu.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
??Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com>
---
.../man-db/{man-db_2.9.2.bb => man-db_2.9.3.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-extended/man-db/{man-db_2.9.2.bb => man-db_2.9.3.bb} (95%)
diff --git a/meta/recipes-extended/man-db/man-db_2.9.2.bb b/meta/recipes-extended/man-db/man-db_2.9.3.bb
similarity index 95%
rename from meta/recipes-extended/man-db/man-db_2.9.2.bb
rename to meta/recipes-extended/man-db/man-db_2.9.3.bb
index 53ebc85922..0e6016a73c 100644
--- a/meta/recipes-extended/man-db/man-db_2.9.2.bb
+++ b/meta/recipes-extended/man-db/man-db_2.9.3.bb
@@ -7,7 +7,7 @@ LIC_FILES_CHKSUM = "file://docs/COPYING.LIB;md5=a6f89e2100d9b6cdffcea4f398e37343
SRC_URI = "${SAVANNAH_NONGNU_MIRROR}/man-db/man-db-${PV}.tar.xz \
file://99_mandb \
file://man_db.conf-avoid-multilib-install-file-conflict.patch"
-SRC_URI[sha256sum] = "7b383f26c67525205f96a4a3bfb27993396992794adda6fe05ad565f369f047c"
+SRC_URI[sha256sum] = "fa5aa11ab0692daf737e76947f45669225db310b2801a5911bceb7551c5597b8"
DEPENDS = "libpipeline gdbm groff-native base-passwd"
RDEPENDS_${PN} += "base-passwd"
--
2.17.1?
[-- Attachment #2: Type: text/html, Size: 2098 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 man-db: upgrade 2.9.2 -> 2.9.3 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=1592990515965.50599@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.