[wplug] Perl upgrade breaks spamassassin --lint

[Brandon Kuczenski]

Hi all.  I just made a routine adjustment to my spamassassin rules and ran 
spamassassin --lint in the name of good practices to test the file.

To my surprise, it failed rather dramatically.  The output is:

$ spamassassin --lint
Can't locate HTML/Parser.pm in @INC (@INC contains: 
/usr/local/lib/perl5/site_perl/5.8.2 
/usr/local/lib/perl5/site_perl/5.8.6/mach 
/usr/local/lib/perl5/site_perl/5.8.6 /usr/local/lib/perl5/site_perl/5.005 
/usr/local/lib/perl5/site_perl /usr/local/lib/perl5/5.8.6/BSDPAN 
/usr/local/lib/perl5/5.8.6/mach /usr/local/lib/perl5/5.8.6) at 
/usr/local/lib/perl5/site_perl/5.8.2/Mail/SpamAssassin/HTML.pm line 7.
BEGIN failed--compilation aborted at 
/usr/local/lib/perl5/site_perl/5.8.2/Mail/SpamAssassin/HTML.pm line 7.
Compilation failed in require at 
/usr/local/lib/perl5/site_perl/5.8.2/Mail/SpamAssassin/PerMsgStatus.pm 
line 42.
BEGIN failed--compilation aborted at 
/usr/local/lib/perl5/site_perl/5.8.2/Mail/SpamAssassin/PerMsgStatus.pm 
line 42.
Compilation failed in require at 
/usr/local/lib/perl5/site_perl/5.8.2/Mail/SpamAssassin.pm line 62.
BEGIN failed--compilation aborted at 
/usr/local/lib/perl5/site_perl/5.8.2/Mail/SpamAssassin.pm line 62.
Compilation failed in require at /usr/local/bin/spamassassin line 69.

The peculiar thing is: spamassassin (when run as spamd) still works.  It 
still sorts my messages appropriately and so on.  And it doesn't complain 
at boot time, and there's nothing in the logs.  I suppose the problem has 
something to do with the fact that SpamAssassin is running in 
site_perl/5.8.2 when the current version is perl 5.8.6 (a security 
vulnerability necessitated an upgrade).

I've never understood much about perl as an operating environment (as 
opposed to perl as a language) ... most people just say "run cpan and 
install SpamAssassin -- it's fun and easy!" and, in fact, that is what I 
did.  So I don't really know where to start -- in Perl, in SpamAssassin, 
in some kind of environment variable... etc.

So .. is this a problem?  I don't like to ignore things just because they 
"seem to still work."

Thanks for any tips,
Brandon