From: Bernd Kuhls <bernd@kuhls.net>
To: buildroot@buildroot.org
Subject: [Buildroot] [PATCH/next 1/1] package/sqlite: bump version to 3.43.0
Date: Mon, 28 Aug 2023 18:30:03 +0200 [thread overview]
Message-ID: <20230828163003.818942-1-bernd@kuhls.net> (raw)
Release notes: https://sqlite.org/releaselog/3_43_0.html
Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
---
package/sqlite/sqlite.hash | 2 +-
package/sqlite/sqlite.mk | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/package/sqlite/sqlite.hash b/package/sqlite/sqlite.hash
index 39758f2b43..1a7f47edcd 100644
--- a/package/sqlite/sqlite.hash
+++ b/package/sqlite/sqlite.hash
@@ -1,3 +1,3 @@
# Locally computed
-sha256 7abcfd161c6e2742ca5c6c0895d1f853c940f203304a0b49da4e1eca5d088ca6 sqlite-autoconf-3420000.tar.gz
+sha256 49008dbf3afc04d4edc8ecfc34e4ead196973034293c997adad2f63f01762ae1 sqlite-autoconf-3430000.tar.gz
sha256 66e056b6e8687f32af30d5187611b98b12a8f46f07aaf62f43585f276e8f0ac9 tea/license.terms
diff --git a/package/sqlite/sqlite.mk b/package/sqlite/sqlite.mk
index 1576d6a3e1..5e676d5387 100644
--- a/package/sqlite/sqlite.mk
+++ b/package/sqlite/sqlite.mk
@@ -4,8 +4,8 @@
#
################################################################################
-SQLITE_VERSION = 3.42.0
-SQLITE_TAR_VERSION = 3420000
+SQLITE_VERSION = 3.43.0
+SQLITE_TAR_VERSION = 3430000
SQLITE_SOURCE = sqlite-autoconf-$(SQLITE_TAR_VERSION).tar.gz
SQLITE_SITE = https://www.sqlite.org/2023
SQLITE_LICENSE = Public domain
--
2.39.2
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-08-28 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 16:30 Bernd Kuhls [this message]
2023-08-29 12:54 ` [Buildroot] [PATCH/next 1/1] package/sqlite: bump version to 3.43.0 Thomas Petazzoni via buildroot
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=20230828163003.818942-1-bernd@kuhls.net \
--to=bernd@kuhls.net \
--cc=buildroot@buildroot.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