From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] libsoup: upgrade 3.0.4 -> 3.0.5
Date: Mon, 28 Mar 2022 17:52:52 +0800 [thread overview]
Message-ID: <1648461173-15770-4-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1648461173-15770-1-git-send-email-wangmy@fujitsu.com>
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
.../libsoup/{libsoup_3.0.4.bb => libsoup_3.0.5.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-support/libsoup/{libsoup_3.0.4.bb => libsoup_3.0.5.bb} (94%)
diff --git a/meta/recipes-support/libsoup/libsoup_3.0.4.bb b/meta/recipes-support/libsoup/libsoup_3.0.5.bb
similarity index 94%
rename from meta/recipes-support/libsoup/libsoup_3.0.4.bb
rename to meta/recipes-support/libsoup/libsoup_3.0.5.bb
index 775ab29ddd..d2535c91a2 100644
--- a/meta/recipes-support/libsoup/libsoup_3.0.4.bb
+++ b/meta/recipes-support/libsoup/libsoup_3.0.5.bb
@@ -12,7 +12,7 @@ DEPENDS = "glib-2.0 glib-2.0-native libxml2 sqlite3 libpsl nghttp2"
SHRT_VER = "${@d.getVar('PV').split('.')[0]}.${@d.getVar('PV').split('.')[1]}"
SRC_URI = "${GNOME_MIRROR}/libsoup/${SHRT_VER}/libsoup-${PV}.tar.xz"
-SRC_URI[sha256sum] = "5bd38b5e091f707fd7fa3ed7c37aacca3f8e16c65787f1cc17dc38d1dcde567b"
+SRC_URI[sha256sum] = "f5d143db6830b3825edc2a1c4449d639273b0bfa017a4970871962d9bca22145"
PROVIDES = "libsoup-3.0"
CVE_PRODUCT = "libsoup"
--
2.25.1
next prev parent 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 [OE-core] [PATCH] glib-networking: upgrade 2.70.1 -> 2.72.0 Wang Mingyu
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 ` Wang Mingyu [this message]
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-4-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