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 E2BF01FF136 for ; Mon, 09 Mar 2026 21:52:31 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 46B19ACFA; Mon, 9 Mar 2026 21:52:21 +0100 (CET) From: Thomas Lamprecht To: pbs-devel@lists.proxmox.com, Maximiliano Sandoval Subject: applied: [pbs-devel] [PATCH proxmox 05/10] cargo: set resolver to 3 Date: Mon, 9 Mar 2026 21:52:03 +0100 Message-ID: <177308950285.805486.6106192695776581284.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260126151349.627829-6-m.sandoval@proxmox.com> References: <20260126151349.627829-1-m.sandoval@proxmox.com> <20260126151349.627829-6-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: 1773089501312 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.266 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: U2QCGXK66QJNXC7XO43RQTAGYK7EESV7 X-Message-ID-Hash: U2QCGXK66QJNXC7XO43RQTAGYK7EESV7 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 Backup Server development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Mon, 26 Jan 2026 16:13:42 +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! [05/10] cargo: set resolver to 3 commit: fc930afa617c8e137d0ac95d32027903d03875e8