From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 8A3A61FF398 for ; Mon, 27 May 2024 13:16:56 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 9C3961FD; Mon, 27 May 2024 13:17:18 +0200 (CEST) Date: Mon, 27 May 2024 13:17:16 +0200 (CEST) From: Christian Ebner To: Proxmox Backup Server development discussion , Dominik Csapak Message-ID: <2029511145.416.1716808636167@webmail.proxmox.com> In-Reply-To: <15af5b0d-05a3-4d89-b8f3-d1788ea38c28@proxmox.com> References: <20240514103421.289431-1-c.ebner@proxmox.com> <20240514103421.289431-62-c.ebner@proxmox.com> <40542da1-4552-477e-8880-02f2d1eff904@proxmox.com> <787720807.679.1716459433622@webmail.proxmox.com> <15af5b0d-05a3-4d89-b8f3-d1788ea38c28@proxmox.com> MIME-Version: 1.0 X-Priority: 3 Importance: Normal X-Mailer: Open-Xchange Mailer v7.10.6-Rev64 X-Originating-Client: open-xchange-appsuite X-SPAM-LEVEL: Spam detection results: 0 AWL 0.031 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: Re: [pbs-devel] [PATCH v6 proxmox-backup 61/65] client: pxar: add archive creation with reference test X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox Backup Server development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pbs-devel-bounces@lists.proxmox.com Sender: "pbs-devel" > On 27.05.2024 13:05 CEST Christian Ebner wrote: > Had a closer look at this, the archive itself is just fine and the files > can be restored without any problems when adding the payload input to a > `pxar extract` command, so it seems rather to be a regression in the > `pxar list`. I do however still have to figure out what the exact issue is. The issue is that the decoder has no payload input attached, therefore skipping over the size of the file payload in the metadata archive rather than the payload input during the dumping. I will have to force to attach the payload input as well here in case of a split archive. So the test itself is fine. _______________________________________________ pbs-devel mailing list pbs-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel