public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Anuj Mittal <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 4/9] sqlite3: upgrade 3.44.2 -> 3.45.1
Date: Fri, 16 Feb 2024 19:40:29 +0800	[thread overview]
Message-ID: <20240216114034.109257-4-anuj.mittal@intel.com> (raw)
In-Reply-To: <20240216114034.109257-1-anuj.mittal@intel.com>

Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
---
 .../sqlite/{sqlite3_3.44.2.bb => sqlite3_3.45.1.bb}           | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-support/sqlite/{sqlite3_3.44.2.bb => sqlite3_3.45.1.bb} (62%)

diff --git a/meta/recipes-support/sqlite/sqlite3_3.44.2.bb b/meta/recipes-support/sqlite/sqlite3_3.45.1.bb
similarity index 62%
rename from meta/recipes-support/sqlite/sqlite3_3.44.2.bb
rename to meta/recipes-support/sqlite/sqlite3_3.45.1.bb
index 459884a5581..2ca8bc5bc9a 100644
--- a/meta/recipes-support/sqlite/sqlite3_3.44.2.bb
+++ b/meta/recipes-support/sqlite/sqlite3_3.45.1.bb
@@ -3,8 +3,8 @@ require sqlite3.inc
 LICENSE = "PD"
 LIC_FILES_CHKSUM = "file://sqlite3.h;endline=11;md5=786d3dc581eff03f4fd9e4a77ed00c66"
 
-SRC_URI = "http://www.sqlite.org/2023/sqlite-autoconf-${SQLITE_PV}.tar.gz"
-SRC_URI[sha256sum] = "1c6719a148bc41cf0f2bbbe3926d7ce3f5ca09d878f1246fcc20767b175bb407"
+SRC_URI = "http://www.sqlite.org/2024/sqlite-autoconf-${SQLITE_PV}.tar.gz"
+SRC_URI[sha256sum] = "cd9c27841b7a5932c9897651e20b86c701dd740556989b01ca596fcfa3d49a0a"
 
 CVE_STATUS[CVE-2023-36191] = "disputed: The error is a bug. It has been fixed upstream. But it is not a vulnerability"
 
-- 
2.43.2



  parent reply	other threads:[~2024-02-16 11:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-16 11:40 [PATCH 1/9] enchant2: upgrade 2.6.5 -> 2.6.7 Anuj Mittal
2024-02-16 11:40 ` [PATCH 2/9] minicom: upgrade 2.8 -> 2.9 Anuj Mittal
2024-02-17 12:38   ` [OE-core] " Richard Purdie
2024-02-19  8:11     ` Mittal, Anuj
2024-02-16 11:40 ` [PATCH 3/9] libproxy: upgrade 0.5.3 -> 0.5.4 Anuj Mittal
2024-02-16 11:40 ` Anuj Mittal [this message]
2024-02-16 11:40 ` [PATCH 5/9] orc: upgrade 0.4.36 -> 0.4.37 Anuj Mittal
2024-02-16 11:40 ` [PATCH 6/9] stress-ng: upgrade 0.17.04 -> 0.17.05 Anuj Mittal
2024-02-16 11:40 ` [PATCH 7/9] swig: upgrade 4.1.1 -> 4.2.0 Anuj Mittal
2024-02-17  2:59   ` [OE-core] " Khem Raj
2024-02-18  3:01     ` Khem Raj
2024-02-19  2:50       ` Mittal, Anuj
2024-02-19  4:19         ` Khem Raj
2024-02-16 11:40 ` [PATCH 8/9] gstreamer1.0: upgrade 1.22.9 -> 1.22.10 Anuj Mittal
2024-02-16 11:40 ` [PATCH 9/9] libcap-ng: fix build with swig 4.2.0 Anuj Mittal

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=20240216114034.109257-4-anuj.mittal@intel.com \
    --to=anuj.mittal@intel.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