On Sun, Mar 28, 2021 at 11:47:34AM +0000, Laura Smith wrote: > Running sa-compile (may take a long time) > chmod: changing permissions of > '/var/lib/spamassassin/compiled/5.028/3.004002/Mail/SpamAssassin/CompiledRegexps/body_0.pm': > Operation not permitted > dpkg: error processing package sa-compile (--configure): > installed sa-compile package post-installation script subprocess returned > error exit status 1 > Errors were encountered while processing: > sa-compile > E: Sub-process /usr/bin/dpkg returned an error code (1) > $ ls -l > /var/lib/spamassassin/compiled/5.028/3.004002/Mail/SpamAssassin/CompiledRegexps/body_0.pm > -r--r--r-- 1 root root 32641 Aug 25 2020 > /var/lib/spamassassin/compiled/5.028/3.004002/Mail/SpamAssassin/CompiledRegexps/body_0.pm > $ ls -l /var/lib/spamassassin/compiled/5.028/3.004002/Mail/SpamAssassin/ > total 0 > drwxr-xr-x 2 debian-spamd debian-spamd 23 Aug 25 2020 CompiledRegexps
/var/lib/spamassassin/compiled/5.028/3.004002/Mail/SpamAssassin/CompiledRegexps/body_0.pm isn't owned by root in a default installation of spamassassin. Most likely somebody previously ran sa-compile as root on your system, rather than as the 'debian-spamd' user that's used by the daily cron job. That is known to break things right now. The workaround is to delete the root-owned file and let sa-compile recreate it. The spamassassin packages need to do a better job of recovering from or preventing this scenario, but at the moment they don't. noah
