Bug 698364 - spamassassin doesn't work well with Perl 5.12.x
Summary: spamassassin doesn't work well with Perl 5.12.x
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: spamassassin
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Warren Togami
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-20 17:54 UTC by Marcela Mašláňová
Modified: 2011-08-14 00:28 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-08-14 00:28:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Marcela Mašláňová 2011-04-20 17:54:14 UTC
spamassassin doesn't have check section in specfile. I suppose running this test suite on koji is not easy, but we could notice that spamassassin didn't pass many test with Perl 5.12.

Upstream matrix report:
http://matrix.cpantesters.org/?dist=Mail-SpamAssassin+3.3.1

And blog entry about it:
http://blogs.perl.org/users/steffen_schwigon/2011/04/perl-qa-hackathon-2011---day-1-1.html

Comment 1 Kevin Fenzi 2011-04-22 17:30:28 UTC
Ideally we would like to see these fixed upstream and then we can enable check in our spec. ;) 

It sounds like you made progress on fixing things and offered to get those merged upstream, which is great!

Comment 2 Warren Togami 2011-04-22 18:05:23 UTC
Rawhide has 3.3.1?  I thought it had a snapshot of 3.3.2 which fixes the perl-5.12 issues?  In any case 3.3.2 is coming soonish.

Comment 3 Marcela Mašláňová 2011-04-26 06:58:11 UTC
(In reply to comment #1)
> Ideally we would like to see these fixed upstream and then we can enable check
> in our spec. ;) 
> 
> It sounds like you made progress on fixing things and offered to get those
> merged upstream, which is great!

It's just fyi, new version of Perl 5.14.0 will be released soon. I relied on test suites, so I fix only those, which can't be built ;-)

Comment 4 Nick Bebout 2011-08-14 00:28:03 UTC
3.3.3 is now in stable, I believe this should be fixed now.

Comment 5 Nick Bebout 2011-08-14 00:28:15 UTC
3.3.2 I mean.


Note You need to log in before you can comment on or make changes to this bug.