From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] libdazzle: upgrade 3.42.0 -> 3.44.0
Date: Tue, 22 Mar 2022 18:38:06 +0800 [thread overview]
Message-ID: <1647945489-5242-1-git-send-email-wangmy@fujitsu.com> (raw)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
.../libdazzle/{libdazzle_3.42.0.bb => libdazzle_3.44.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-gnome/libdazzle/{libdazzle_3.42.0.bb => libdazzle_3.44.0.bb} (88%)
diff --git a/meta/recipes-gnome/libdazzle/libdazzle_3.42.0.bb b/meta/recipes-gnome/libdazzle/libdazzle_3.44.0.bb
similarity index 88%
rename from meta/recipes-gnome/libdazzle/libdazzle_3.42.0.bb
rename to meta/recipes-gnome/libdazzle/libdazzle_3.44.0.bb
index a10acc6ada..49ebc818b0 100644
--- a/meta/recipes-gnome/libdazzle/libdazzle_3.42.0.bb
+++ b/meta/recipes-gnome/libdazzle/libdazzle_3.44.0.bb
@@ -12,7 +12,7 @@ inherit gnomebase upstream-version-is-even vala features_check gobject-introspec
DEPENDS = "glib-2.0-native glib-2.0 gtk+3"
-SRC_URI[archive.sha256sum] = "eae67a3b3d9cce408ee9ec0ab6adecb83e52eb53f9bc93713f4df1e84da16925"
+SRC_URI[archive.sha256sum] = "3cd3e45eb6e2680cb05d52e1e80dd8f9d59d4765212f0e28f78e6c1783d18eae"
GIR_MESON_OPTION = 'with_introspection'
--
2.25.1
next reply other threads:[~2022-03-22 10:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 10:38 Wang Mingyu [this message]
2022-03-22 10:38 ` [OE-core] [PATCH] libhandy: upgrade 1.5.0 -> 1.6.1 Wang Mingyu
2022-03-23 4:52 ` Alexandre Belloni
2022-03-22 10:38 ` [OE-core] [PATCH] libjitterentropy: upgrade 3.3.1 -> 3.4.0 Wang Mingyu
2022-03-22 17:13 ` Alexandre Belloni
2022-03-22 10:38 ` [OE-core] [PATCH] libsolv: upgrade 0.7.21 -> 0.7.22 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=1647945489-5242-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