Subject: | 4.034 breaks SpamAssassin |
After upgrading from NetAddr-IP 4.033 to 4.034, SpamAssassin 3.3.1 fails
to start. Here's a sample of the errors:
Oct 28 10:31:34 mail-1 spamd[8077]: netset: cannot include
0:0:0:0:0:0:0:1/128 as it has already been included
Oct 28 10:31:35 mail-1 spamd[8077]: netset: cannot include
0:0:0:0:0:0:0:1/128 as it has already been included
Oct 28 10:31:35 mail-1 spamd[8080]: netset: cannot include <network1>/24
as it has already been included
Oct 28 10:31:35 mail-1 spamd[8080]: netset: cannot include <network2>/24
as it has already been included
Oct 28 10:31:35 mail-1 spamd[8080]: netset: cannot include <host1>/32 as
it has already been included
Oct 28 10:31:35 mail-1 spamd[8080]: netset: cannot include <host2>/32 as
it has already been included
it looks like Mark Martinec has found a test that zeroes in on the
breakage:
http://permalink.gmane.org/gmane.mail.spam.spamassassin.general/131120
correct (NetAddr-IP-4.033):
$ perl -le 'use NetAddr::IP; print NetAddr::IP->new6("127.0.0.0/8")'
0:0:0:0:0:0:7F00:0/104
wrong (NetAddr-IP-4.034):
$ perl -le 'use NetAddr::IP; print NetAddr::IP->new6("127.0.0.0/8")'
0:0:0:0:0:0:7F00:0/8
I can confirm that downgrading to 4.033 eliminates the problem.
-Steve
--
Steve Huff (SHUFF) * shuff@cpan.org