From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 5DB5C1FF141 for ; Mon, 30 Mar 2026 18:07:13 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 73A424F6C; Mon, 30 Mar 2026 18:07:22 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Maximiliano Sandoval Subject: applied: [pve-devel] [PATCH installer] cargo: Bump resolver to 3 Date: Mon, 30 Mar 2026 18:06:39 +0200 Message-ID: <177488679683.2104600.7634053847347493269.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260126123456.256917-1-m.sandoval@proxmox.com> References: <20260126123456.256917-1-m.sandoval@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1774886751233 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.258 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 KAM_NUMSUBJECT 0.5 Subject ends in numbers excluding current years 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: HK3RX2XDLYJEBHH4UJHHRX7IOFWX6NAN X-Message-ID-Hash: HK3RX2XDLYJEBHH4UJHHRX7IOFWX6NAN X-MailFrom: t.lamprecht@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 VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Mon, 26 Jan 2026 13:34:40 +0100, Maximiliano Sandoval wrote: > This is the default since edition 2024 which the crate uses. See > https://doc.rust-lang.org/edition-guide/rust-2024/cargo-resolver.html > for more details. > > Do note that removing the key would result in: > > warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2024 which implies `resolver = "3"` > note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest > note: to use the edition 2024 resolver, specify `workspace.resolver = "3"` in the workspace root's manifest > note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions > > [...] Applied, thanks! [1/1] cargo: Bump resolver to 3 commit: a3b11702793b00202add2e15a6c973af22463b8c