On 8/9/26 2:57 PM, David Runge wrote:
Hi David,
thanks for bringing this issue to our attention!
I've created the change that causes your issue, because the previous integration
would run `sa-compile` as root in a `post_upgrade` function (see also the
individual commit messages in [spamassassin!3], which describe this change).
I believe to have fixed the issue you are reporting with [spamassassin!4].
Somewhat related: To update and compile the spamassassin rules, you can now
rely on spamassassin-update.service and spamassassin-update.timer, which gravely
simplifies the integration (see the ArchWiki section on [updating rules]).
Thanks David,
When I saw you were the culprit, I knew it was in good hands. I do
use the spamassassin-update.timer provided in the wiki, and have had no
issues with it. Occasionally I do run update/compile manually if I see
something odd in pacman update output or in the journal -- more as a
check and confirm.
On the issue of doing `chown -R spamd: /var/lib/spamassassin` to
change all the ownership from root to spamd, is there any problem or
reason not to do that? That was just my "do what pacman wanted"
solution, but I don't know if it could have unwanted side-effects (I
don't think so, and so far it hasn't, but I'm no expert on what
spamassassin does behind the scenes)
Thanks for your maintenance of the package and you reply.
--
David C. Rankin, J.D.,P.E.
