Re: Issues after upgrade Debian from sarge to etch [SOLVED]
Hello! > Hmm... I know you said standard Etch packages but those versions do > not match the versions in Etch. They match the versions in Testing. > Therefore I conclude that you are actually running Debian testing. > Didn't think so but obviously I must mess things up while experimenting with amavisd-new (and spamassassin plugins). > For various reasons I recommend Debian Stable (currently Etch) or > Debian Unstable (always named Sid). I can't recommend Testing for > production use. > I know and I agree - my sources.list is only linked to etch - but maybe there was a short time when I had "testing" in it. > Please check and see if you have SA installed multiple different ways, > by package and by direct installation (e.g. CPAN). If you have > multiple versions of SpamAssassin installed I suggest removing all of > the ones that you are not using. Bob, you made my day - thank you! After checking my installation with your hints I could cleanup some cpan-installed modules and replaced the testing-version with the version from the etch repository. Finally I got rid of this error messages. Thank you all for your help! Stefan signature.asc Description: OpenPGP digital signature
Re: Issues after upgrade Debian from sarge to etch
Stefan Hoth wrote: > Since I upgraded my box to debian etch I have the same errors day by day. > > I'm running SpamAssassin version 3.2.0 running on Perl version 5.8.8 > (standard etch-package) with amavisd-new-2.4.2 (20060627) (also etch-pack). Hmm... I know you said standard Etch packages but those versions do not match the versions in Etch. They match the versions in Testing. Therefore I conclude that you are actually running Debian testing. For various reasons I recommend Debian Stable (currently Etch) or Debian Unstable (always named Sid). I can't recommend Testing for production use. > Command: test -e /usr/sbin/amavisd-new-cronjob && > /usr/sbin/amavisd-new-cronjob sa-sync > ... > plugin: failed to parse plugin (from @INC): Bareword > "Mail::SpamAssassin::Constants::CHARSETS_LIKELY_TO_FP_AS_CAPS" not > allowed while "strict subs" in use at > /usr/local/share/perl/5.8.8/Mail/SpamAssassin/Plugin/HeaderEval.pm line 965. > Compilation failed in require at (eval 70) line 1. Because this file is installed in /usr/local I know that it is not the Debian packaged version but is instead a direct local installation. That is fine. But this is an indication of a typical problem. Often when multiple versions of perl modules are installed simultaneously this will create version mismatch problems. It is certainly possible to install multiple versions but there have also been a lot of reports of problems in those cases too. > Since I'm barely familiar to perl I couldn't get my self rid of these > errors. Although spamassassin and amavis work fine together. Please check and see if you have SA installed multiple different ways, by package and by direct installation (e.g. CPAN). If you have multiple versions of SpamAssassin installed I suggest removing all of the ones that you are not using. Bob