public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] sqlite3: upgrade 3.38.1 -> 3.38.2
Date: Mon, 28 Mar 2022 17:55:28 +0800	[thread overview]
Message-ID: <1648461328-15808-3-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1648461328-15808-1-git-send-email-wangmy@fujitsu.com>

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
 .../sqlite/{sqlite3_3.38.1.bb => sqlite3_3.38.2.bb}             | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-support/sqlite/{sqlite3_3.38.1.bb => sqlite3_3.38.2.bb} (86%)

diff --git a/meta/recipes-support/sqlite/sqlite3_3.38.1.bb b/meta/recipes-support/sqlite/sqlite3_3.38.2.bb
similarity index 86%
rename from meta/recipes-support/sqlite/sqlite3_3.38.1.bb
rename to meta/recipes-support/sqlite/sqlite3_3.38.2.bb
index 54b04d620e..a37aff6fe7 100644
--- a/meta/recipes-support/sqlite/sqlite3_3.38.1.bb
+++ b/meta/recipes-support/sqlite/sqlite3_3.38.2.bb
@@ -4,7 +4,7 @@ LICENSE = "PD"
 LIC_FILES_CHKSUM = "file://sqlite3.h;endline=11;md5=786d3dc581eff03f4fd9e4a77ed00c66"
 
 SRC_URI = "http://www.sqlite.org/2022/sqlite-autoconf-${SQLITE_PV}.tar.gz"
-SRC_URI[sha256sum] = "8e3a8ceb9794d968399590d2ddf9d5c044a97dd83d38b9613364a245ec8a2fc4"
+SRC_URI[sha256sum] = "e7974aa1430bad690a5e9f79a6ee5c8492ada8269dc675875ad0fb747d7cada4"
 
 # -19242 is only an issue in specific development branch commits
 CVE_CHECK_IGNORE += "CVE-2019-19242"
-- 
2.25.1



      parent reply	other threads:[~2022-03-28  9:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-28  9:55 [OE-core] [PATCH] lttng-ust: upgrade 2.13.1 -> 2.13.2 Wang Mingyu
2022-03-28  9:55 ` [OE-core] [PATCH] msmtp: upgrade 1.8.19 -> 1.8.20 Wang Mingyu
2022-03-28  9:55 ` Wang Mingyu [this message]

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=1648461328-15808-3-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