Am 05.11.24 um 12:43 schrieb Fabian Grünbichler: > to avoid the need to mark every package shipping PVE-related perl code as > activating the explicit trigger. the explicit trigger can still be used for > packages that need to reload the API without shipping a perl module > > the explicit trigger activation can be dropped in PVE 9.0 in packages that > ship > perl code, without a need for versioned dependencies.
Not for the HA usecase. > > Signed-off-by: Fabian Grünbichler <f.gruenbich...@proxmox.com> > --- > Currently, the following packages ship perl modules in /usr/share/perl5/PVE, > but don't activate the explicit trigger: > > libpve-apiclient-perl libpve-cluster-perl libpve-notify-perl pve-cluster > libpve-u2f-server-perl dab At least for libpve-notify-perl it might be nice to get a trigger so that HA get's restarted there too, most of the rest it would be rather superfluous for HA. > > libpve-cluster-perl is upgraded in lockstep with libpve-cluster-api-perl, > which does activate the trigger. > > manually tested reinstalling `pve-cluster` with and without this patch, seems > to work as expected. > > are there other paths that might make sense to "watch"? > > debian/triggers | 1 + > 1 file changed, 1 insertion(+) > > applied, thanks! Korrigieren Schließen Rechtschreibung Possible spelling mistake found. use caseIgnorieren _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
