https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7618
Ondrej Lysonek <ondrej.lyso...@seznam.cz> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ondrej.lyso...@seznam.cz
--- Comment #23 from Ondrej Lysonek <ondrej.lyso...@seznam.cz> ---
Hi everyone,
(In reply to Sidney Markowitz from comment #22)
> The only workaround would be to
> patch sa-update like RedHat is proposing to do in
> https://bugzilla.redhat.com/show_bug.cgi?id=1787382
>
> BTW, I don't think RedHat's approach is a good idea. We have made sure that
> rule updates work with old versions, including conditionals as necessary,
> but with this change the backwards compatibility will no longer be tested
> and IMO should not be counted on.
In the 3.4.2 announcement [1] it said the following, which I understood to mean
that the rules would continue to be compatible with spamassassin >= 3.3.2.
"This means that while
we produce rule updates with the focus on them working for any release from
v3.3.2 forward, they will start failing SHA-1 validation for sa-update."
Am I misunderstanding something, or has the position of the SpamAssassin
project changed with regard to this?
Due to the late phase of its lifecycle, packages cannot be rebased to newer
versions in RHEL-7. So it would be lovely if the rules remained compatible with
older spamassassin versions.
[1]
https://lists.apache.org/thread.html/1ac11532235b5459aa16c4e9d636bf4aa0b141d347d1361e40cc1b78@%3Cannounce.apache.org%3E
--
You are receiving this mail because:
You are the assignee for the bug.
