From patchwork Wed May 11 08:40:17 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: Adolf Belka X-Patchwork-Id: 5610 Return-Path: Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) client-signature ECDSA (P-384)) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by web04.haj.ipfire.org (Postfix) with ESMTPS id 4KypJQ4WNQz3x1v for ; Wed, 11 May 2022 08:40:22 +0000 (UTC) Received: from mail02.haj.ipfire.org (mail02.haj.ipfire.org [172.28.1.201]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) client-signature ECDSA (P-384)) (Client CN "mail02.haj.ipfire.org", Issuer "R3" (verified OK)) by mail01.ipfire.org (Postfix) with ESMTPS id 4KypJQ0Y2Mz45v; Wed, 11 May 2022 08:40:22 +0000 (UTC) Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4KypJQ0NNVz2ydg; Wed, 11 May 2022 08:40:22 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) client-signature ECDSA (P-384)) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4KypJP21M3z2xd2 for ; Wed, 11 May 2022 08:40:21 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4KypJP0bKjz45v; Wed, 11 May 2022 08:40:21 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1652258421; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=KwJcShka8B90pufGEIg0JHKA8YIglJ2L9b31tRybV58=; b=hxvS7fxpS2yFsFcnuHFEQmWuwKhpWNMG/RBsCEggKTcNTgwlO0GHTvy2TfMFwsCttW1kon +U8hBRMWvIaBdQBQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1652258421; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=KwJcShka8B90pufGEIg0JHKA8YIglJ2L9b31tRybV58=; b=qOnbR2bqbfdjLrd3UblM/vt1ymCCqT/tNb/8X+E7z27Di2J376UxUbuNlifecqyvJYzhHw MHpNAoHbgfae31n8+ZmrKJYSfeSnTvax9lLKQ8/9cqd5YyC1RKL5Wx94Rb4u5RwlV/bvy2 ivG+knC4ZHjiLHOaSiFbJyQPlCw4VD7B5HqbXE2D0f/4RKJeV0ZcFSuWXNj1kOJ5kcV1oo f6nPtp5VtB6Yb3ZaI+871cqDPL0XRgijk7VQaq1JP9rKPvxc1sygjqyeICYsaygXwQGsIO KZHUGIJvhFdMetbzR/gTMnW3YgmMt41LZwkMG4JhKsEhuLAXWs3M90v3Tdoyfw== From: Adolf Belka To: development@lists.ipfire.org Subject: [PATCH] sqlite: Update to version 3380500 Date: Wed, 11 May 2022 10:40:17 +0200 Message-Id: <20220511084017.4026-1-adolf.belka@ipfire.org> MIME-Version: 1.0 X-BeenThere: development@lists.ipfire.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IPFire development talk List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: development-bounces@lists.ipfire.org Sender: "Development" - 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 Reviewed-by: Peter Müller --- 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)