From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Stoiko Ivanov <s.ivanov@proxmox.com>, pmg-devel@lists.proxmox.com
Subject: [pmg-devel] applied-series: [PATCH spamassassin/pmg-api] add trigger to reload pmg-api services on spamassassin updates
Date: Fri, 21 Feb 2025 18:38:34 +0100 [thread overview]
Message-ID: <bf06abb8-6b24-49b1-8c19-74cd96fd7f5a@proxmox.com> (raw)
In-Reply-To: <20240612171018.18240-1-s.ivanov@proxmox.com>
Am 12.06.24 um 19:10 schrieb Stoiko Ivanov:
> While running some internal tests with the recently released SpamAssassin
> 4.0.1 I noticed that pmg-smtp-filter did not get restarted upon upgrading
> the package.
> This has not really been noticed until now, as we ship new
> proxmox-spamassassin versions mostly with our point-releases, which do
> contain updated versions of pmg-api anyways.
>
> Tested minimally by building both packages with the patches, installing an
> updated pmg-api and afterwards installing the updated
> proxmox-spamassassin, while verifying that the services indeed get
> restarted on my test-machine.
>
> proxmox-spamassassin:
> Stoiko Ivanov (1):
> d/triggers: add trigger to restart pmg services
>
> debian/triggers | 1 +
> 1 file changed, 1 insertion(+)
> create mode 100644 debian/triggers
>
> pmg-api:
> Stoiko Ivanov (1):
> d/triggers: add interest in spamassassin updates
>
> debian/triggers | 1 +
> 1 file changed, 1 insertion(+)
>
applied series, thanks!
_______________________________________________
pmg-devel mailing list
pmg-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel
prev parent reply other threads:[~2025-02-21 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 17:10 [pmg-devel] " Stoiko Ivanov
2024-06-12 17:10 ` [pmg-devel] [PATCH pmg-api 1/1] d/triggers: add interest in " Stoiko Ivanov
2024-06-12 17:10 ` [pmg-devel] [PATCH spamassassin 1/1] d/triggers: add trigger to restart pmg services Stoiko Ivanov
2025-02-21 17:38 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bf06abb8-6b24-49b1-8c19-74cd96fd7f5a@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pmg-devel@lists.proxmox.com \
--cc=s.ivanov@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox