public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] man-db: upgrade 2.10.1 -> 2.10.2
Date: Tue, 22 Mar 2022 18:39:45 +0800	[thread overview]
Message-ID: <1647945587-5282-1-git-send-email-wangmy@fujitsu.com> (raw)

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
 .../man-db/{man-db_2.10.1.bb => man-db_2.10.2.bb}               | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-extended/man-db/{man-db_2.10.1.bb => man-db_2.10.2.bb} (96%)

diff --git a/meta/recipes-extended/man-db/man-db_2.10.1.bb b/meta/recipes-extended/man-db/man-db_2.10.2.bb
similarity index 96%
rename from meta/recipes-extended/man-db/man-db_2.10.1.bb
rename to meta/recipes-extended/man-db/man-db_2.10.2.bb
index e8fd47a8f7..a41e2dd4d8 100644
--- a/meta/recipes-extended/man-db/man-db_2.10.1.bb
+++ b/meta/recipes-extended/man-db/man-db_2.10.2.bb
@@ -9,7 +9,7 @@ SRC_URI = "${SAVANNAH_NONGNU_MIRROR}/man-db/man-db-${PV}.tar.xz \
            file://99_mandb \
            file://0001-man-Move-local-variable-declaration-to-function-scop.patch \
            file://man_db.conf-avoid-multilib-install-file-conflict.patch"
-SRC_URI[sha256sum] = "2ffd8f2e80122fe72e60c740c851e6a3e15c9a7921185eb4752c1c672824bed6"
+SRC_URI[sha256sum] = "ee97954d492a13731903c9d0727b9b01e5089edbd695f0cdb58d405a5af5514d"
 
 DEPENDS = "libpipeline gdbm groff-native base-passwd"
 RDEPENDS:${PN} += "base-passwd"
-- 
2.25.1



             reply	other threads:[~2022-03-22 10:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22 10:39 Wang Mingyu [this message]
2022-03-22 10:39 ` [OE-core] [PATCH] python3-markupsafe: upgrade 2.1.0 -> 2.1.1 Wang Mingyu
2022-03-22 10:39 ` [OE-core] [PATCH] vala: upgrade 0.54.7 -> 0.56.0 Wang Mingyu

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=1647945587-5282-1-git-send-email-wangmy@fujitsu.com \
    --to=wangmy@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