From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 84DCD9D9B8 for ; Mon, 5 Jun 2023 17:43:23 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 604C12A4AC for ; Mon, 5 Jun 2023 17:43:23 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Mon, 5 Jun 2023 17:43:22 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 4B98248AB0 for ; Mon, 5 Jun 2023 17:43:22 +0200 (CEST) From: Fiona Ebner To: pve-devel@lists.proxmox.com Date: Mon, 5 Jun 2023 17:43:07 +0200 Message-Id: <20230605154313.181289-1-f.ebner@proxmox.com> X-Mailer: git-send-email 2.39.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.048 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: [pve-devel] [PATCH-SERIES proxmox-apt/widget-toolkit] prepare for major upgrade X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jun 2023 15:43:23 -0000 There's a confusing issue when the suites are already updated, because the UI will not detect any Proxmox VE repository anymore then. This is fixed by the proxmox-apt patch intended for the stable branch. The UI patches make sure the ignore-pre-upgrade-warning is actually ignored and add a check for mixed repositories when upgrade is allowed. The final UI patch is intended for the stable branch only and makes sure that the warning handling expects a major upgrade to be allowed. proxmox-apt: Fiona Ebner (1): repositories: also detect repository with next suite as configured src/repositories/mod.rs | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) proxmox-widget-toolkit: Fiona Ebner (5): apt repositories: actually ignore ignore-pre-upgrade-warning apt repositories: just ignore unknown info rather than throwing an error apt repositories: add classifyOrigin helper apt repositories: detect mixed suites before major upgrade apt repositoires: allow major upgrade src/node/APTRepositories.js | 63 ++++++++++++++++++++++++++++++------- 1 file changed, 52 insertions(+), 11 deletions(-) -- 2.39.2