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 96D8B1FF0C2 for ; Thu, 22 Oct 2026 14:21:27 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id B85562175C; Thu, 22 Oct 2026 14:17:32 +0200 (CEST) From: Lukas Wagner To: pbs-devel@lists.proxmox.com, pve-devel@lists.proxmox.com Subject: [PATCH proxmox-perl-rs v5 32/42] debian: document versioned break for PVE::RS::Notify changes Date: Thu, 22 Oct 2026 14:15:57 +0200 Message-ID: <20261022121608.271515-33-l.wagner@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261022121608.271515-1-l.wagner@proxmox.com> References: <20261022121608.271515-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: 1792671374491 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.260 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: 5Q7ROYZM7LCHGFXGH5MURQVCYRB5IZYA X-Message-ID-Hash: 5Q7ROYZM7LCHGFXGH5MURQVCYRB5IZYA 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. If the versioned break is deemed to annoying, we could ship a module alias so that it can still be imported as Proxmox::RS::Notify, and add some magic to the API functions so that both, explicitly enumerating parameters as well as passing the parameter struct are supported. Personally, I think a break is less hassle than going back later to clean up these 'crutches'. 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..2a76b13 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.6), pve-ha-manager (<< 5.0.6~~), - pve-manager (<< 7.2-8), + pve-manager (<< 9.2.21), 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