From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] sudo: upgrade 1.9.10 -> 1.9.11
Date: Wed, 15 Jun 2022 16:19:50 +0800 [thread overview]
Message-ID: <1655281192-6663-1-git-send-email-wangmy@fujitsu.com> (raw)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
meta/recipes-extended/sudo/{sudo_1.9.10.bb => sudo_1.9.11.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-extended/sudo/{sudo_1.9.10.bb => sudo_1.9.11.bb} (96%)
diff --git a/meta/recipes-extended/sudo/sudo_1.9.10.bb b/meta/recipes-extended/sudo/sudo_1.9.11.bb
similarity index 96%
rename from meta/recipes-extended/sudo/sudo_1.9.10.bb
rename to meta/recipes-extended/sudo/sudo_1.9.11.bb
index aa0d814ed7..5e97d8a2cc 100644
--- a/meta/recipes-extended/sudo/sudo_1.9.10.bb
+++ b/meta/recipes-extended/sudo/sudo_1.9.11.bb
@@ -8,7 +8,7 @@ SRC_URI = "https://www.sudo.ws/dist/sudo-${PV}.tar.gz \
PAM_SRC_URI = "file://sudo.pam"
-SRC_URI[sha256sum] = "44a1461098e7c7b8e6ac597499c24fb2e43748c0c139a8b4944e57d1349a64f4"
+SRC_URI[sha256sum] = "b5476e30d83ca14734da9370f2206beb21c8a33fc85a504fb8a61d18d8b351be"
DEPENDS += " virtual/crypt ${@bb.utils.contains('DISTRO_FEATURES', 'pam', 'libpam', '', d)}"
RDEPENDS:${PN} += " ${@bb.utils.contains('DISTRO_FEATURES', 'pam', 'pam-plugin-limits pam-plugin-keyinit', '', d)}"
--
2.25.1
next reply other threads:[~2022-06-15 8:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 8:19 Wang Mingyu [this message]
2022-06-15 8:19 ` [OE-core] [PATCH] piglit: upgrade to latest revision Wang Mingyu
2022-06-15 8:19 ` [OE-core] [PATCH] stress-ng: upgrade 0.14.01 -> 0.14.02 Wang Mingyu
2022-06-16 7:30 ` [OE-core] [PATCH] sudo: upgrade 1.9.10 -> 1.9.11 Alexandre Belloni
2022-06-16 7:37 ` Alexandre Belloni
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=1655281192-6663-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