>From the log: Running sa-compile (may take a long time) Jul 23 17:27:26.363 [1356] info: config: failed to parse line, skipping, in "/etc/spamassassin/local.cf": use_dcc 0 sa-compile: not compiling; 'spamassassin --lint' check failed! ESC[1mdpkg:ESC[0m error processing package sa-compile (--configure): installed sa-compile package post-installation script subprocess returned error exit status 2
The default config does not contain that valie: # grep -v '#' /etc/spamassassin/local.cf | uniq ifplugin Mail::SpamAssassin::Plugin::Shortcircuit That said the broken config breaks the upgrade. I'm no sa expert, worst case this was working with the old version and the newer version doesn#t like the config anymore? But TBH in most cases scripts or users changed something in the past, didn't touch it since then and on an upgrade due to the recompile the message pops up. In any of these cases fixing the config is the right way out which will unblock the upgrades. @chris - you might have a different but similar issue with the config being invalid? If it is different I'd recommend a new bug so that this one stays on just one topic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783343 Title: package sa-compile 3.4.1-8build1 failed to install/upgrade: installed sa-compile package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1783343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
