Noah Meyerhans wrote: > Per http://marc.info/?l=spamassassin-users&m=141728529723698&w=2 it > sounds like we might be spared these warnings for a bit.
This has such high visibility that I have no doubt that the upstream updates will contain a fix of some sort. Even if that is due to it being disabled. But Joanne has suggested a good fix. http://article.gmane.org/gmane.mail.spam.spamassassin.general/146276 Joanne wrote: if version > 3.004001 && perl_version >= 5.010000 body NON_588_COMPATIBLE_RE_SYNTAX /\w++/ endif I believe that will go into the upstream. Hopefully in the next update cycle. I tested it locally. > We'll still need to get fixes into all releases, because eventually > the rule that triggers this warning (and other rules using the same > functionality) will be re-enabled. I think what will happen is that rules will use something more like the above syntax moving forward. This will gate rules such as to enable them in newer SpamAssassin versions but disable them in older ones. The effect will be microscopically small for a long time in older versions as they don't get a particular new rule. Only time will tell if a particular new rule is important or not. I suspect that only very few rules will require such gating. So I am not sure it is required to do anything more at this moment other than wait for the upstream to fix the sa-update feed. Bob -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
