Log messages like this can be observed while processing emails by spamassassin after perl upgrade: "/usr/lib64/perl5/vendor_perl/5.18.2/Mail/SpamAssassin/AsyncLoop.pm line 363," <<<snip>>> " Use of each() on hash after insertion without resetting hash iterator results in undefined behavior at" The problem has an upstream bug report with a patch attached: https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6937 Please consider to include the upstream patch in portage until it arrives. Reproducible: Always
Confirmed by upstream, patch already available. Ref. https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6937
3.4 is in the tree, maybe we should get it stable then?
(In reply to Manuel Rüger from comment #2) > 3.4 is in the tree, maybe we should get it stable then? 3.4 isn't affected, no fix is needed. It would be good to stabilize it, at least as perl-5.18.2 gets stable on a given architecture. Thx: Dw.
(In reply to Attila Tóth from comment #3) > (In reply to Manuel Rüger from comment #2) > > 3.4 is in the tree, maybe we should get it stable then? > > 3.4 isn't affected, no fix is needed. It would be good to stabilize it, at > least as perl-5.18.2 gets stable on a given architecture. > OK let's do exactly this. Not cc'ing arches yet, since we first need to finish the rekeywording... :(
Actually its maybe easier to backport the fixes. Let's go for 3.3.2-r5 instead.
*** Bug 518858 has been marked as a duplicate of this bug. ***
Arches please test and stabilize mail-filter/spamassassin-3.3.2-r5 Only difference to -r4 is an upstream patch for Perl 5.18 compatibility Target: all stable arches
Stable for HPPA.
amd64 stable
x86 stable
ppc stable
ppc64 stable
ia64 stable
sparc stable
alpha stable
arm stable, all arches done.