On 2026-08-05 15:41:25 (-0500), David C Rankin wrote: > All, > > System update today listed owenership problems with /var/lib/spamassassin > being owned by spamd: but subdirectories owned by root:. This has never been > a problem before as sa-update and sa-compile are run as root. > > The wiki[1] has changed showing these commands run as spamd now, but > provides no information whatesoever on the change or how this is supposed to > be accomplished: > > [spamd]$ /usr/bin/vendor_perl/sa-update && /usr/bin/vendor_perl/sa-compile > > The errors shown when the post-install hook, Creating temporary files are: > > :: Running post-transaction hooks... > ( 1/11) Creating system user accounts... > ( 2/11) Creating temporary files... > Detected unsafe path transition /var/lib/spamassassin (owned by spamd) → > /var/lib/spamassassin/3.004002 (owned by root) during canonicalization of > var/lib/spamassassin/3.004002. > Detected unsafe path transition /var/lib/spamassassin (owned by spamd) → > /var/lib/spamassassin/4.000002 (owned by root) during canonicalization of > var/lib/spamassassin/4.000002. > Detected unsafe path transition /var/lib/spamassassin (owned by spamd) → > /var/lib/spamassassin/compiled (owned by root) during canonicalization of > var/lib/spamassassin/compiled. > Detected unsafe path transition /var/lib/spamassassin (owned by spamd) → > /var/lib/spamassassin/3.004004 (owned by root) during canonicalization of > var/lib/spamassassin/3.004004. > Detected unsafe path transition /var/lib/spamassassin (owned by spamd) → > /var/lib/spamassassin/3.004006 (owned by root) during canonicalization of > var/lib/spamassassin/3.004006. > Detected unsafe path transition /var/lib/spamassassin (owned by spamd) → > /var/lib/spamassassin/3.004003 (owned by root) during canonicalization of > var/lib/spamassassin/3.004003. > error: command failed to execute correctly > > What is the new preferred way to run sa-update && sa-compile as user > spamd? su? sudo? or some new systemd doas? > > > [1] https://wiki.archlinux.org/title/SpamAssassin > > -- > David C. Rankin, J.D.,P.E. >
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]). Best, David P.S.: Please make sure to report issues on the issue tracker of the respective package instead, as it may go unnoticed on the mailing list for a while. [spamassassin!3]: https://gitlab.archlinux.org/archlinux/packaging/packages/spamassassin/-/merge_requests/3/commits [spamassassin!4]: https://gitlab.archlinux.org/archlinux/packaging/packages/spamassassin/-/merge_requests/4 [updating rules]: https://wiki.archlinux.org/title/SpamAssassin#Updating_rules
signature.asc
Description: PGP signature
