sqlite: Update to version 3380500

Message ID 20220511084017.4026-1-adolf.belka@ipfire.org
State Accepted
Commit efb7528e3ff2a0cf8f1a6f6eec4bcb20b3ae7986
Headers show
Series sqlite: Update to version 3380500 | expand

Commit Message

Adolf Belka May 11, 2022, 8:40 a.m. UTC
- 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@ipfire.org>
---
 lfs/sqlite | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

Comments

Peter Müller May 30, 2022, 7:28 p.m. UTC | #1
Reviewed-by: Peter Müller <peter.mueller@ipfire.org>

> - 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@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)
>

Patch

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)