public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] sqlite: Update to version 3380500
Date: Wed, 11 May 2022 10:40:17 +0200	[thread overview]
Message-ID: <20220511084017.4026-1-adolf.belka@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1869 bytes --]

- Update from version 3380300 to 3380500
- Update of rootfile not required
- Changelog
   Version 3.38.5
     The 3.38.4 patch release included a minor change to the CLI source code that did not
      work. The release manager only ran a subset of the normal release tests, and hence
      did not catch the problem. As a result, the CLI will segfault when using columnar
      output modes in version 3.38.4. This blunder did not affect the core SQLite library.
      It only affected the CLI.
     Take-away lesson: Always run all of your tests prior to a release - even a trival
      patch release. Always.
     The 3.38.5 patch release fixes the 3.38.4 blunder.
   Version 3.38.4
     Another user-discovered problem in the new Bloom filter optimization is fixed in this
      patch release. Without the fix, it is possible for a multi-way join that uses a
      Bloom filters for two or more tables in the join to enter an infinite loop if the
      key constraint on one of those tables contains a NULL value.

Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
 lfs/sqlite | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/lfs/sqlite b/lfs/sqlite
index 076943280..4f6d5ad06 100644
--- a/lfs/sqlite
+++ b/lfs/sqlite
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 3380300
+VER        = 3380500
 
 THISAPP    = sqlite-autoconf-$(VER)
 DL_FILE    = $(THISAPP).tar.gz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = 35271246a27597ce88b4eaa1ff483b42421371737b5fe357eb6d2ad1d9c543b2d60341f7ee63f7dc95e374f61c539a607472b53881027c843b0da07704dd200f
+$(DL_FILE)_BLAKE2 = 546db2fddfc065ddb5d0f232456a79d6a582cd98acfe7c1c8e0f53311906f70d47d89dfabfdb52c9c261202931b97d84b5fd238f70e6539522e56a57c03036b3
 
 install : $(TARGET)
 
-- 
2.36.0


             reply	other threads:[~2022-05-11  8:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11  8:40 Adolf Belka [this message]
2022-05-30 19:28 ` Peter Müller

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=20220511084017.4026-1-adolf.belka@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.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