pve-manager commit 27d1db3a ("triggers: add path-based trigger
interest") added a path-based interest and states:> 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. Signed-off-by: Fiona Ebner <[email protected]> --- If we expect the package to stop shipping Perl code at some point, maybe it is better to just keep it? debian/pve-firewall.triggers | 1 - 1 file changed, 1 deletion(-) diff --git a/debian/pve-firewall.triggers b/debian/pve-firewall.triggers index ea8e9e2..4294b34 100644 --- a/debian/pve-firewall.triggers +++ b/debian/pve-firewall.triggers @@ -1,2 +1 @@ -activate-noawait pve-api-updates interest-noawait /usr/share/perl5/PVE -- 2.47.3
