From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 13200 invoked from network); 15 Jan 2021 22:41:44 -0000 Received: from lists.zx2c4.com (165.227.139.114) by inbox.vuxu.org with ESMTPUTF8; 15 Jan 2021 22:41:44 -0000 Received: by lists.zx2c4.com (ZX2C4 Mail Server) with ESMTP id c4a7f584; Fri, 15 Jan 2021 22:41:26 +0000 (UTC) Return-Path: Received: from pinero.vault24.org (pinero.vault24.org [69.164.212.126]) by lists.zx2c4.com (ZX2C4 Mail Server) with ESMTPS id 0ad3b19b (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO) for ; Fri, 15 Jan 2021 22:41:22 +0000 (UTC) Received: from feynman.vault24.org (c-98-243-50-21.hsd1.mi.comcast.net [98.243.50.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by pinero.vault24.org (Postfix) with ESMTPS id 42C8B61FB for ; Fri, 15 Jan 2021 17:41:21 -0500 (EST) Received: by feynman.vault24.org (Postfix, from userid 1000) id 6E0A2302DCE3; Fri, 15 Jan 2021 17:41:20 -0500 (EST) Date: Fri, 15 Jan 2021 17:41:20 -0500 From: Jon DeVree To: cgit@lists.zx2c4.com Subject: Re: cgit 1.2.3: lighttpd 1.4.57, AlpineLinux [edge]: using cache breaks delivery Message-ID: Mail-Followup-To: cgit@lists.zx2c4.com References: <20201221162619.wYrRU%steffen@sdaoden.eu> <20210115215110.b5qdf6dzubklgzic@chatter.i7.local> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20210115215110.b5qdf6dzubklgzic@chatter.i7.local> X-BeenThere: cgit@lists.zx2c4.com X-Mailman-Version: 2.1.30rc1 Precedence: list List-Id: List for cgit developers and users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: cgit-bounces@lists.zx2c4.com Sender: "CGit" On Fri, Jan 15, 2021 at 16:51:10 -0500, Konstantin Ryabitsev wrote: > Going through bug backlinks, there's a claim that 5.10.4 fixes the problem -- > is that accurate, or is the bug still present? > 5.10.4 was the first 5.10 kernel uploaded to Debian Sid which is how I discovered the issue. It was still broken on the vanilla 5.10.7 kernel that I installed this morning to see if it was fixed yet. -- Jon Doge Wrangler X(7): A program for managing terminal windows. See also screen(1) and tmux(1).