From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pmg-devel@lists.proxmox.com
Subject: [pmg-devel] [PATCH spamassassin/pmg-api] add trigger to reload pmg-api services on spamassassin updates
Date: Wed, 12 Jun 2024 19:10:16 +0200 [thread overview]
Message-ID: <20240612171018.18240-1-s.ivanov@proxmox.com> (raw)
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(+)
--
2.39.2
_______________________________________________
pmg-devel mailing list
pmg-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel
next reply other threads:[~2024-06-12 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 17:10 Stoiko Ivanov [this message]
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 ` [pmg-devel] applied-series: [PATCH spamassassin/pmg-api] add trigger to reload pmg-api services on spamassassin updates Thomas Lamprecht
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=20240612171018.18240-1-s.ivanov@proxmox.com \
--to=s.ivanov@proxmox.com \
--cc=pmg-devel@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.