From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id B22A71FF09C for ; Mon, 02 Nov 2026 16:04:23 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 9A36221DF6; Mon, 02 Nov 2026 15:58:51 +0100 (CET) From: Lukas Wagner To: pbs-devel@lists.proxmox.com, pve-devel@lists.proxmox.com Subject: [PATCH proxmox-perl-rs v6 32/43] debian: document versioned break for PVE::RS::Notify changes Date: Mon, 2 Nov 2026 15:57:29 +0100 Message-ID: <20261102145748.411817-33-l.wagner@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261102145748.411817-1-l.wagner@proxmox.com> References: <20261102145748.411817-1-l.wagner@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1793631474397 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.241 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust 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: Z3EXVU4L6F7FU4AWUVWJKJ24N2UGW5ZX X-Message-ID-Hash: Z3EXVU4L6F7FU4AWUVWJKJ24N2UGW5ZX X-MailFrom: l.wagner@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: Signed-off-by: Lukas Wagner --- Notes: @MAINTAINERS: Please change the version numbers as needed. I've tried an alternative approach where instead of moving Proxmox:RS::Notify to PVE::RS::Notify, it was just copied, with the changes in the API only perfomed in the copy; however it turned out that this merely moved the versioned break *up* the stack, while at the same time producing the need for cleanup work in the future. So I think breaking here once is actually the best solution, unfortunately. pve-rs/debian/control | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pve-rs/debian/control b/pve-rs/debian/control index 70367dc..3b5075d 100644 --- a/pve-rs/debian/control +++ b/pve-rs/debian/control @@ -67,9 +67,9 @@ Depends: libproxmox-rs-perl (>= 0.3.5), Breaks: libpve-access-control (<< 7.1-3), libpve-common-perl (<< 7.1-4), libpve-network-perl (<< 1.4.0), - libpve-notify-perl (<< 8.0.7), + libpve-notify-perl (<< 9.1.8), pve-ha-manager (<< 5.0.6~~), - pve-manager (<< 7.2-8), + pve-manager (<< 9.2.25), Description: PVE parts which have been ported to Rust - Rust source code This package contains the source for the Rust pve-rs crate, packaged by debcargo for use with cargo and dh-cargo. -- 2.47.3