Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 73612

Summary: spamassassin does not work with perl version upgrade
Product: Gentoo Linux Reporter: Park Ji-in <tisphie>
Component: Current packagesAssignee: Gentoo Perl team <perl>
Status: RESOLVED DUPLICATE    
Severity: minor    
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Park Ji-in 2004-12-06 18:36:54 UTC
cat /usr/bin/spamd | head -n 1
#!/usr/bin/perl5.8.4 -w

and other executionable are also.

so, when i upgrade my perl to 5.8.5, it does not run.

Reproducible: Always
Steps to Reproduce:
1. install spamassassin
2. upgrade perl version
3. try to run spamassassin

Actual Results:  
 # spamassassin
-bash: /usr/bin/spamassassin: /usr/bin/perl5.8.4: bad interpreter: No such file
or directory

It does not run.

Expected Results:  
It should run
Comment 1 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2004-12-06 21:34:18 UTC
Looks like you failed to run the libperl rebuilder script as noted by the end of the perl merge.
Comment 2 Park Ji-in 2004-12-06 21:53:33 UTC
note after perl merge says,

If this is an upgrade to a perl 5.6.1 system,
~OR~ an upgrade to a previous Gentoo release
of perl 5.8.0, prior to -r8 
you may need to recompile applications that
were emerged against the old libperl.so

AND, I just did minor upgrade 5.8.4->5.8.5 and there should not be libperl.so problem.

that warning message isn't enough. and even though, interpreter declare in spamassasin script 

#!/usr/bin/perl5.8.5 -w 
is not good form, isnt it?

other perl script like auto-tools or anything do

#!/usr/bin/perl or #!/usr/bin/perl -w
Comment 3 Malte S. Stretz 2004-12-10 16:48:40 UTC
Yeah, that's a known problem with SpamAssassin's Makefile.PL and Perl -- it doesn't always auto-detect the perl binary correctly.  There's a patch in bug 62276 for which I still hope that somebody will create a 2.64-r1 ebuild...

*** This bug has been marked as a duplicate of 62276 ***