From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pdm-devel-bounces@lists.proxmox.com>
Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40])
	by lore.proxmox.com (Postfix) with ESMTPS id 0F1271FF0F1
	for <inbox@lore.proxmox.com>; Mon, 13 Jul 2026 10:06:25 +0200 (CEST)
Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1])
	by gate001.proxmox.com (Proxmox) with ESMTP id 8358921346;
	Mon, 13 Jul 2026 10:06:24 +0200 (CEST)
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
Date: Mon, 13 Jul 2026 10:06:19 +0200
Message-Id: <DJXAEET9QUUC.3S8YW4XZXPDHM@proxmox.com>
Subject: Re: [PATCH datacenter-manager 13/15] task cache: trigger repair of
 corruption when compressing archive files
From: "Lukas Wagner" <l.wagner@proxmox.com>
To: "Dominik Csapak" <d.csapak@proxmox.com>, "Lukas Wagner"
 <l.wagner@proxmox.com>, <pdm-devel@lists.proxmox.com>
X-Mailer: aerc 0.21.0-0-g5549850facc2-dirty
References: <20260702092258.174740-1-l.wagner@proxmox.com>
 <20260702092258.174740-14-l.wagner@proxmox.com>
 <6cff14e4-0b10-493f-b8c5-a8f6199e5f74@proxmox.com>
In-Reply-To: <6cff14e4-0b10-493f-b8c5-a8f6199e5f74@proxmox.com>
X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2
X-Bm-Transport-Timestamp: 1783929964597
X-SPAM-LEVEL: Spam detection results:  0
	AWL                     0.344 Adjusted score from AWL reputation of From:
 address
	DMARC_MISSING             0.1 Missing DMARC policy
	KAM_DMARC_STATUS         0.01 Test Rule for DKIM or SPF Failure with Strict
 Alignment (newer systems)
	RCVD_IN_DNSWL_LOW        -0.7 Sender listed at https://www.dnswl.org/,
 low trust
	SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
	SPF_PASS               -0.001 SPF: sender matches SPF record
Message-ID-Hash: U4UCWR7V54WS4LONRAY7WST6SEBW4SSQ
X-Message-ID-Hash: U4UCWR7V54WS4LONRAY7WST6SEBW4SSQ
X-MailFrom: l.wagner@proxmox.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop;
 banned-address; emergency; member-moderation; nonmember-moderation;
 administrivia; implicit-dest; max-recipients; max-size; news-moderation;
 no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.10
Precedence: list
List-Id: Proxmox Datacenter Manager development discussion
 <pdm-devel.lists.proxmox.com>
List-Help: <mailto:pdm-devel-request@lists.proxmox.com?subject=help>
List-Owner: <mailto:pdm-devel-owner@lists.proxmox.com>
List-Post: <mailto:pdm-devel@lists.proxmox.com>
List-Subscribe: <mailto:pdm-devel-join@lists.proxmox.com>
List-Unsubscribe: <mailto:pdm-devel-leave@lists.proxmox.com>

On Fri Jul 10, 2026 at 1:36 PM CEST, Dominik Csapak wrote:
> if i'm reading this right, this not only triggers the repair,
> but changes the compression from one implemenation to the one in
> the archivefilewriter?
>
> if yes, we should either mention it in the commit, or
> split that out into a separate one

I'll be sure to include the rationale in the commit message!

Thanks!