Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 249668 - mail-filter/spamassassin-fuzzyocr-3.5.1-r1 - FuzzyOCR O_NONBLOCK Exporter.pm Perl Error
Summary: mail-filter/spamassassin-fuzzyocr-3.5.1-r1 - FuzzyOCR O_NONBLOCK Exporter.pm ...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Tom Knight (RETIRED)
URL: http://fuzzyocr.own-hero.net/ticket/411
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-03 00:47 UTC by VinnieNZ
Modified: 2009-11-13 15:33 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
New ebuild (spamassassin-fuzzyocr-3.5.1-r2.ebuild,5.38 KB, text/plain)
2008-12-03 00:49 UTC, VinnieNZ
Details
Patch file (exporter.patch,1.46 KB, patch)
2008-12-03 00:51 UTC, VinnieNZ
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description VinnieNZ 2008-12-03 00:47:10 UTC
When running spamassassin --lint on a mail machine using mail-filter/spamassassin-fuzzyocr-3.5.1-r1 I receive the error:

Subroutine FuzzyOcr::O_NONBLOCK redefined at /usr/lib/perl5/5.8.8/Exporter.pm line 65.
at /usr/lib/perl5/5.8.8/i686-linux/POSIX.pm line 19

I found a patch available for the error at http://fuzzyocr.own-hero.net/ticket/411 so have added this to the ebuild.

This fixed the issue for me.

Reproducible: Always

Steps to Reproduce:
1.  spamassassin --lint
2.
3.

Actual Results:  
Subroutine FuzzyOcr::O_NONBLOCK redefined at /usr/lib/perl5/5.8.8/Exporter.pm line 65.
 at /usr/lib/perl5/5.8.8/i686-linux/POSIX.pm line 19

Expected Results:  
That spamassassin --lint returns no result
Comment 1 VinnieNZ 2008-12-03 00:49:04 UTC
Created attachment 174125 [details]
New ebuild
Comment 2 VinnieNZ 2008-12-03 00:51:17 UTC
Created attachment 174127 [details, diff]
Patch file
Comment 3 Bernard Cafarelli gentoo-dev 2009-11-13 15:33:46 UTC
Fixed with the version bump to 3.6.0, which has this patch already included

Thanks for the report!