From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] glib-networking: upgrade 2.70.1 -> 2.72.0
Date: Mon, 28 Mar 2022 17:52:49 +0800 [thread overview]
Message-ID: <1648461173-15770-1-git-send-email-wangmy@fujitsu.com> (raw)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
.../{glib-networking_2.70.1.bb => glib-networking_2.72.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-core/glib-networking/{glib-networking_2.70.1.bb => glib-networking_2.72.0.bb} (93%)
diff --git a/meta/recipes-core/glib-networking/glib-networking_2.70.1.bb b/meta/recipes-core/glib-networking/glib-networking_2.72.0.bb
similarity index 93%
rename from meta/recipes-core/glib-networking/glib-networking_2.70.1.bb
rename to meta/recipes-core/glib-networking/glib-networking_2.72.0.bb
index 44bc08f159..d578f17aa5 100644
--- a/meta/recipes-core/glib-networking/glib-networking_2.70.1.bb
+++ b/meta/recipes-core/glib-networking/glib-networking_2.72.0.bb
@@ -9,7 +9,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=4fbd65380cdd255951079008b364516c"
SECTION = "libs"
DEPENDS = "glib-2.0"
-SRC_URI[archive.sha256sum] = "2a16bfc2d271ccd3266e3fb462bc8a4103c02e81bbb339aa92d6fb060592d7bc"
+SRC_URI[archive.sha256sum] = "100aaebb369285041de52da422b6b716789d5e4d7549a3a71ba587b932e0823b"
PACKAGECONFIG ??= "openssl ${@bb.utils.contains('PTEST_ENABLED', '1', 'tests', '', d)}"
--
2.25.1
next reply other threads:[~2022-03-28 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 9:52 Wang Mingyu [this message]
2022-03-28 9:52 ` [OE-core] [PATCH] iproute2: upgrade 5.16.0 -> 5.17.0 Wang Mingyu
2022-03-28 9:52 ` [OE-core] [PATCH] libevdev: upgrade 1.12.0 -> 1.12.1 Wang Mingyu
2022-03-28 9:52 ` [OE-core] [PATCH] libsoup: upgrade 3.0.4 -> 3.0.5 Wang Mingyu
2022-03-28 9:52 ` [OE-core] [PATCH] lttng-modules: upgrade 2.13.2 -> 2.13.3 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=1648461173-15770-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