https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8306
Noah Meyerhans <fr...@morgul.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |fr...@morgul.net
Resolution|--- |WONTFIX
--- Comment #2 from Noah Meyerhans <fr...@morgul.net> ---
> Leaving this open as others with more imagination may see an actually better
> behavior in this circumstance. My instinct says this is a problem for
> downstream packagers to address, as it is essentially an external failure in
> the install process.
I think that's reasonable. It's definitely an edge case. In the standard
installation process, sa-update must complete successfully in order for
SpamAssassin to run, so it's unlikely to come up there.
I can avoid this in the distro package by making the installation process look
more like an offline installation with respect to the default ruleset. That is,
I'd install the bundled rules using sa-update as documented in the offline
variant of "Installing Rules" in the INSTALL doc. This will ensure a
successful sa-update run even if the cached rules are in use.
--
You are receiving this mail because:
You are the assignee for the bug.
