From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] atk: upgrade 2.36.0 -> 2.38.0
Date: Mon, 28 Mar 2022 17:49:38 +0800 [thread overview]
Message-ID: <1648460981-15712-2-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1648460981-15712-1-git-send-email-wangmy@fujitsu.com>
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
meta/recipes-support/atk/{atk_2.36.0.bb => atk_2.38.0.bb} | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
rename meta/recipes-support/atk/{atk_2.36.0.bb => atk_2.38.0.bb} (84%)
diff --git a/meta/recipes-support/atk/atk_2.36.0.bb b/meta/recipes-support/atk/atk_2.38.0.bb
similarity index 84%
rename from meta/recipes-support/atk/atk_2.36.0.bb
rename to meta/recipes-support/atk/atk_2.38.0.bb
index 59913f4bd0..62fec9abf8 100644
--- a/meta/recipes-support/atk/atk_2.36.0.bb
+++ b/meta/recipes-support/atk/atk_2.38.0.bb
@@ -15,7 +15,6 @@ DEPENDS = "gettext-native glib-2.0"
GNOMEBASEBUILDCLASS = "meson"
inherit gnomebase gtk-doc gettext upstream-version-is-even gobject-introspection
-SRC_URI[archive.md5sum] = "01aa5ec5138f5f8c9b3a4e3196ed2900"
-SRC_URI[archive.sha256sum] = "fb76247e369402be23f1f5c65d38a9639c1164d934e40f6a9cf3c9e96b652788"
+SRC_URI[archive.sha256sum] = "ac4de2a4ef4bd5665052952fe169657e65e895c5057dffb3c2a810f6191a0c36"
BBCLASSEXTEND = "native nativesdk"
--
2.25.1
next prev parent reply other threads:[~2022-03-28 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 9:49 [OE-core] [PATCH] apt: upgrade 2.4.0 -> 2.4.3 Wang Mingyu
2022-03-28 9:49 ` Wang Mingyu [this message]
2022-03-28 9:49 ` [OE-core] [PATCH] cronie: upgrade 1.5.7 -> 1.6.0 Wang Mingyu
2022-03-28 9:49 ` [OE-core] [PATCH] diffoscope: upgrade 207 -> 208 Wang Mingyu
2022-03-28 9:49 ` [OE-core] [PATCH] dpkg: upgrade 1.21.2 -> 1.21.4 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=1648460981-15712-2-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