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 5C79A9F6F0 for ; Fri, 9 Jun 2023 10:50:00 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 3D5DD2B667 for ; Fri, 9 Jun 2023 10:49:30 +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 ; Fri, 9 Jun 2023 10:49:29 +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 7F28842ACE for ; Fri, 9 Jun 2023 10:49:29 +0200 (CEST) Message-ID: Date: Fri, 9 Jun 2023 10:49:26 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 To: Wolfgang Bumiller Cc: pve-devel@lists.proxmox.com References: <20230605154313.181289-1-f.ebner@proxmox.com> <20230605154313.181289-2-f.ebner@proxmox.com> Content-Language: en-US From: Fiona Ebner In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.002 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 NICE_REPLY_A -0.091 Looks like a legit reply (A) 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: [pve-devel] [PATCH stable proxmox-apt 1/1] repositories: also detect repository with next suite as configured 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: Fri, 09 Jun 2023 08:50:00 -0000 Am 09.06.23 um 10:45 schrieb Wolfgang Bumiller: > FYI, wrong git repo, should be done in proxmox.git > > Is this purely for stable-only? Yes, sorry if I didn't make that clear. In the Bookworm/master branch, we still want to warn if somebody put the next suite. See also the quick comment about "for next time" below. > > On Mon, Jun 05, 2023 at 05:43:08PM +0200, Fiona Ebner wrote: >> This avoids that no standard Proxmox repository can be detected during >> upgrade anymore. There is a 'ignore-pre-upgrade-warning' about the >> suite already, that the frontend can display when upgrading is not >> allowed yet. >> >> Signed-off-by: Fiona Ebner >> --- >> >> It's not ideal, for the time between when the update for proxmox-apt >> is rolled out and when the Bookworm repositories are actually made >> available. And it would need to be done for each major upgrade. >> >> For next time, I'll try to come up with something better. Probably, >> the callers should let the backend here know when upgrade is allowed >> and then the backend can act accordingly. >>