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 76BB91FF380 for ; Fri, 19 Apr 2024 10:58:31 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 8912E1EC2; Fri, 19 Apr 2024 10:58:31 +0200 (CEST) Message-ID: Date: Fri, 19 Apr 2024 10:57:58 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Lukas Wagner , Proxmox VE development discussion References: <20240409132555.364926-1-l.wagner@proxmox.com> <20240409132555.364926-2-l.wagner@proxmox.com> <95b8c12e-b959-4c4e-93b6-04e91acc3953@proxmox.com> Content-Language: en-US From: Fiona Ebner In-Reply-To: <95b8c12e-b959-4c4e-93b6-04e91acc3953@proxmox.com> X-SPAM-LEVEL: Spam detection results: 0 AWL -0.069 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 SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pve-devel] [PATCH proxmox 01/19] notify: switch to file-based templating system 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: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" Am 19.04.24 um 10:45 schrieb Lukas Wagner: >> Who adds the template files? I don't see a patch for proxmox-ve in this >> series. Does this series require some versioned breaks to some package? > > The pve-manager and pve-ha-manager (for fencing notifications) patches add the templates. > I can't use `/usr/share/pve-manager` and `/usr/share/pve-ha-manager` because > proxmox_notify needs to have a single base directory from where to load template files. > Maybe we should use some other base dir to avoid confusion with the `proxmox-ve` metapackage? > Ah, I see. Yes, maybe a directory named based on libpve-notify-perl would be better or proxmox-notify (but would need to be a bit careful with co-installed PBS and PVE to not create accidental conflicts). > In terms of versions: > pve-{ha}-manager needs to pull in a bumped libpve-notify-perl > libpve-notify-perl needs to pull in bumped libpve-rs-perl/libproxmox-rs-perl > libpve-rs-perl needs to pull in bumped librust-proxmox-notify > > I really wish the dep-chain was a bit easier, yet here we are. > But there also is a need for versioned breaks, right? Because installing new libpve-notify-perl (using new proxmox-perl-rs using new proxmox-notify) without also upgrading pve-manager and pve-ha-manager will be broken or am I missing something? _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel