To test in a more clean way, I manually built libnetaddr-ip-perl_4.035+dfsg-1_amd64.deb using the sources from CPAN and the 4.035 packaging from Debian, and I can confirm the "cannot include" messages from spamassassin are still there, so I guess the fix might have corrected part of the problem, but we are not yet back to 4.033 situation wrt spamassassin.
Could someone with better knowledge of all this reopen the upstream bug after some further analysis? Many thanks in advance. Best, Damien > NetAddr-IP-4.035 should fix this bug, but after upgrading manually > /usr/lib/perl5/NetAddr/IP/Lite.pm to 1.21, I still see the problem when > spamassassin starts, learns new spam or when the daily cron job is > called. > > So not sure the upstream fix in netAddr::IP has cured the initial > problem reported for spamassassin in but 601601. Or maybe I did > something stupid when doing these tests... > > > Best, -- Damien Wyart -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
